We often hear a lot about the core benefits of SOA, which include reuse and agility.
This week, I was in a meeting with Manoo Ordeedolchest, Board Member of Software Park, Thailand, Former President of the Software Industry Promotion Agency (SIPA), Former Dean, The School of Technology, Shinawatra University and a Lecturer at Chulalongkorn University, National Institute of Development Administration (NIDA), as well as other universities.
We were discussing CEP and our proposed CEP Center of Excellence concept for Software Park. One of the topics we touched upon today was CEP “in layman’s terms.” After some brainstorming about CEP, it we were moved to draw a parallel between the SOA and CEP concepts of IT agility and reuse.
Just as SOA is centered around service component reuse and the agility to create new applications from service components quickly and economically; CEP can be considered to be centered around the reuse and sharing of domain knowledge, key indicators (KIs) and other intellectual property (like analytics) when processing events.
In an SOA, we modularize services and a service-component architecture in order to share services and build new applications from these service components.
One of the business goals of CEP is to modularize and standardize declarative programming logic and reuse this logic with event processing platforms from a variety of vendors. This permits both reuse and agility when building event processing applications, at the application logic level versus the SOA service component level.
So, in laymen’s terms CEP can be discussed using the same SOA concepts of reuse and agility, applied to event processing application logic and KIs.
In a future post, I will talk about about CEP and transparency in layman’s terms.