Skip to main content

CEP - CPU of an Enterprise ?

Can CEP can become a CPU of an Enterprise ?

Let us see first what is CEP

With the increasing competitiveness and changing market dynamics, Enterprises are looking for more innovative ways to do business. Lots of emerging capabilities are available for an Enterprise that could help it to keep an edge over its competitor through efficient operation of its business. One such capability is Complex Event Processing.

Even though “Agility” capability will help an Enterprise to drive its business in accordance with the changing market demands, “Real-time Analytics “will help an Enterprise to plan its business more accurately.

Complex Event Processing (CEP) helps an Enterprise to have the real-time analysis capability. CEP is suitable in the scenarios where there is a need to capture a very high volume of events in real-time to perform some analysis and take proactive measures / to make informed decisions. It include capturing more than one event, correlate them and extracting a “meaning” out of it.

Let’s look at this with an example from a lay man point of view. When a plane starts its flight from a source to destination, lots of its parameters such as latitude and longitude, altitude, speed, etc. will start changing continuously at a rapid rate

Here assume that it is configured to emit an event when it’s ground speed change from X miles / hour to X+ 200 miles / hour within a time period of 1 second; Also it is configured to emit an event when it’s altitude drops from some X meters to X-100 meters . These are 2 separate events. When you are able to co-relate these 2 events and extract a “meaning” out of it, it can be used to make a decision.

Say for example, when the altitude drops from 100 meters to 0 meters and its speed shoots up from X to X+200 miles / hour you can co-relate these 2 events and make a meaning out of it – something wrong. A plane’s speed may not shoot up when its altitude drops to zero and hence accordingly a “red alert” alarm can be triggered; Pilot can be warned. A CEP capability is required here to perform such type of processing.

This same type scenario can be applicable for the business / operational data of an Enterprise. As an Enterprise moves through days, weeks, months and quarters of its business, lots of it’s parameters will change and lots of events can be published; Co-relating a no. of individual, isolated events published across an Enterprise will help in understanding on what is actually happening in the system and plan accordingly.

Similar to what an ESB was having a place in Enterprise IT ecosystem; CEP could also find an equal position. When it comes to enabling an Enterprise with a CEP capability, multiple options are available from the platform / product vendors such as Microsoft, IBM, Oracle etc.

Let's see more on technology option for implementing CEP in an Enterprise in the coming posts.


Popular posts from this blog

Lambda Architecture on Microsoft Azure

Gone are those days when Enterprises will wait for hours and days to look at the dashboards based on the old, stale data. In this fast world of BYOD, fitness gears and flooding of other devices, it is becoming super important  to derive out “actionable” information from huge volume of data / noise that is generated from these devices or any other data sources and act proactively on them  in real-time, to stay competitive. At the same time, the need for having dashboards and other analytical capabilities based on the quality, cleansed, processed data still very much exists. With the emergence of more data types and need to handle huge volume, shift is happening from the conventional data warehouse practice to cloud based data processing & management capabilities where high volume batch processing is possible at the optimized cost. Business scenarios demanding the need to process the data in real-time    More  

Heterogeneous Cloud Integration

Heterogeneous integration is common scenario in the Enterprises where their IT portfolio is based on heterogeneous platforms. Various solution approaches such as message broker, messaging middleware, SOA – service based integration were employed to address heterogeneous integration challenges.   These solution approaches were good when the integration happens on premise, with in the data centers of an Enterprise. Problem here is non-availability of “elasticity”.   With the Enterprises started leveraging cloud platforms extensively for various solution aspects such as elastic computing, storage, it opens new capabilities that can be leveraged for heterogeneous integration. Also, similar to existing on premise scenario, Enterprises are also leveraging multiple cloud platforms to address their business needs. This scenario will pose same integration challenges as those that were faced within on premise datacenters   Within datacenters / on premise, integration product

SharePoint 2013 Architectural Trade-Offs

When planning for deploying SharePoint 2013 based Enterprise workloads, it should be done with the consideration / awareness of impact of various architectural decisions what we make. As SharePoint 2013 is a flexible platform providing lots of options in terms of configuration of the existing OOB features and development of custom development solutions to address specific business functional needs, care should be taken when making a particular decision and its impact on overall solution. Even though SharePoint is a matured product, the effectiveness of various business capabilities such as Enterprise Social, Enterprise Search, BI, Document Management, Web Content Management, and Enterprise Content Management that will be delivered based on it, in terms of addressing the business requirements depends on architecture planning. Effectiveness here means performance, security, up-time and other architectural qualities like Scalability, Reliability etc. more ...