Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
While the sessions and discussions on event processing did not have the
global significance of angels on pin heads or the Counter
it did provide a clear indication of just how broadly and deep event
based systems can reach. Whether it's a business application monitoring
mortgage applications, IT
management systems in a Network
Operation Center, bedside monitoring
systems in a hospital or a robot packing pancakes into boxes they all
have a common underpinning, consuming and correlating
Granted, not everyone approaches it with the same
Systems Management people don't think about processing and correlating
events, they think about device management, KPI's, Alerts and the like.
Someone building, managing a business process is likely concerned with
- validating them, stock allocations, warehouses and
Nonetheless, a common framework model behind these systems is event
Two of my favorite sessions at the EPTS Symposium were a panel session
on the EPTS Mission and an open forum on Grand Challenges, a
brainstorming session focused on identifying barriers to the adoption
Four panelists, myself included presented their expectations of the
EPTS and it's role as an industry consortium, it's goals and
what improvements can be made. As a baseline, the EPTS does have a
existing mission statement defined as ...
Given this mission statement and my own expectations there are
number of basic intentions the EPTS should provide to
the uninitiated to event processing:
The EPTS has four working groups that have been active for the last
year: Use-cases, Reference Architecture, Language Analysis and
Glossary. To a large extent the working groups
and are working towards the definition of
CEP that is clear. However, there still a need to highlight
salient value of event processing. For specific vertical
the value of CEP is clear-cut simply because the fit and function is
tailor made. In Capital Markets, for example algo trading has all the
hallmarks of a CEP application - high performance, low latency,
temporal analytics and a streaming data paradigm fit-for-purpose.
However, there are other application domains where CEP is equally
viable but much more subtle. I believe the EPTS can provide a
vendor-neutral taxonomy of event processing - from the basics to the
advanced. Explain why it's unique and different, why language
important and how it is synergistic with a host of other technologies.
To this end, the group has decided to form two new working
to focus on many of these areas. Clearly a forward thinking move.
The Event Processing Technical Society is an organization made of up
both vendors and academics. We're held together by a common thread, a
goal that the whole is greater than the sum of the parts and our
collective will benefit all even as many of us are undeniably
thanks for reading, you can also follow me at twitter, here.
View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.