Simple

Integration of the services is as simple as adding hooks into existing application events. Example: Collecting information about a user connecting to a session by adding 1-2 lines of code to your existing method for handling the connection. From there the Metagame library handles the packet send/response case and notifies your system when the response comes back. All service calls are handled in a universal fashion. Services can be added/expanded on the fly without bringing any systems down for maintenance and without needing to redistribute software in terms of the back-end.

Flexible

The system is built so that interaction with services can take place from in-game, out of game, on the web, mobile, and anywhere else jabber or http can go. We provide a c++ library which enables our services as well as core jabber functionality. We have also worked with java, php, and actionscript libraries to provide services in those environments. It really depends on what the project needs and how accessible you want the services to be.

Real time

Service calls can happen in real-time so for tracking usage patterns for your users you would simply integrate service call hooks into your existing logic and describe the data you'd like to record. This information can then be analyzed and extracted in multiple ways for the user's viewing, the developer's viewing, marketing, business, however you want to use it. Data storage is determined by what data you send. So there is no red tape involved in regards to schema changes.