A full-scale installation of Cubeia GEM span across the entire game network. The games will have to publish the live data to the GEM servers, the main GEM installation is at the network level, and finally, each operator may access its specific data and interact with the main data collector within its own domain.The Birds Eye View
In a game network there's a lot of information that can be more or less hard to get your hands on. Cubeia GEM utilizes complex event processing to find you the information you may not otherwise find. A Cubeia GEM installation spans across the entire gambling network. It integrates with the game servers to collect data from the event cloud, GEM stage servers analyse and process the data, and finally the Customer Experience Manager, or CEM, server is installed at each connected operator, giving them full controll over their customer data. The Component View In order to take part of the vent cloud a GEM installation needs to integrate with the games themselves. This is done in a fail-safe fashion and no processing is done in the game servers. All relevant data, such as hand end results, user login etc, are immediately handed off to the GEM processing stages via a simple HTTP call or via message queues. It is extremely important that the integration of GEM within the network is as transparently as possible. Game play must not be affected even if the GEM stage is not responding. Cubeia has long experience from building fail-safe game systems and will work with the customer engineers to make sure this integration does not interrupt game play in any way. The Process View The GEM complex event processing takes place in one or more computing stages installed parallel to the game servers. Here the incoming stream of events are filtered, processed and then split into several streams depending on the operator of the client generating the event. If an operator is connected to the GEM installation the stream of existing the processing for the operator will be forwarded to its customer experience manager server, again using message queues or HTTP calls for maximum transparency.
The Operator View The stream of events arriving to a connected operator will be fed into the CEM, or customer experience manager. This component adds optional extra processing, splits some of the events for optional graphic representation on a live dashboard, and stores everything into a database. Even though the live data is primarily shown on a dashboard, the CEM server comes with an API for integrating more closely with existing operator back end. Even though the stream of events arriving to the operator is filtered and may be assumed to be significant, it may still generate a significant amount of data. Cubeia can help the operator to implement column databases or ditributed storages in order to handle the load if necessarry. When the events are written to database the operator may use traditional business intelligence methods such as data mining to further process the data. Again, Cubeia is more than happy to assist with this.
|