This is a series of articles that, I hope, provide a bit of color to the workings of Oracle's Complex Event Processing. While event processing has been around for quite some time and is well established in industries such as financial services, many non-financial industries are rapidly expanding their enterprise investment. Consequently, I’m writing articles in two areas: 1) the behavior of the product and 2) event processing patterns.
Product behavior is important, impacting architectural decisions, developer productivity, and long term system maintainability. These articles highlight internal workings not covered in documentation or perhaps not fully illuminated by use cases.
Event processing patterns can be combined in an event processing network (EPN) to solve a particular use case. Interface, responsibility, construction, operation and extension patterns are established software development patterns. With the addition of temporal processing, enabled by the Expression Query Language or Continuous Query Language, a new set of patterns emerge related to time based processing.
It is my hope that these product articles, in combination with higher level design patterns will help you bring event driven applications into production quickly, with a high level of reliability.
1) Event Servers, A Disruptive Technology
2) Object Behavior Within Oracle’s Complex Event Processing Server
