The current big buzzwords in the IT world are: analytics,big data, cloud and mobile. These are believed to be the most influential trends on the IT directions. I have already written about analytics and big data in some previous post, today I'll write on the mobile universe from the point of view of event processing.
Putting the mobile devise symbol on a drawing of an event driven architecture, we can view multiple roles:
- Mobile device can be a producer of events -- this may be both implicit events, using the mobile devise as a sensor and tracking the location of the mobile device over time or explicit events, where a human use mobile devise to report events (such as: traffic jams, completion of tasks, start of the work day)
- Mobile device can also serve as consumer of events -- subscription to either raw or derived events can be manifested within notification in form of Email, SMS, or mobile application. It seems that most uses of mobile devises are the consumer and producer roles. There are also some more sophisticated possible uses, discussed next.
- One can build event processing agent logic using mobile devise, but it is more likely that the use in this case will be to use predefined templates in order to define specific instances of EPA. For example, if the application is subscription to events in my bank account, I might get a template giving me an opportunity to subscribe when my accounts reached a balance of more than X or less than Y, I received a deposit of more than Z, or that the total withdrawals for a single days are more than W. Using the mobile device I can chose any of them and give value to the X, Y, Z, W variables.
- A dashboard showing the real-time state considering the streaming events can be also displayed as a mobile application
- Last but not least -- An EPA can reside on the mobile device itself, collection data and doing some filtering or aggregation.
In a follow-up post I'll try to switch direction and look at event processing from the mobile point of view.
More - later.