Build, protect and deploy apps across any platform and mobile device
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
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
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
computing... it's on everyone's mind these days. Personally I
think it's a term that has attained such aggrandized acclaim that
vendors, analysts, bloggers and anyone with marketing muscle has pulled
and stretched its definition to such and extent that it could mean just
about anything hosted. Cloud Computing Journal polled twenty-one experts to define Cloud Computing.
Just the fact they had to ask the question of twenty-one experts
is rather telling in itself. Well I read what the experts had to
So armed with my newly minted (yet fully stretched, but not of my own making) Cloud definition I happened upon this commentary about CEP in the Cloud or the lack thereof. There's a great quote in the article: "I don’t care where a message is coming from and I don’t care where it’s going”.
Correctly indicated, this in a sense defines a key aspect of CEP.
Event-based applications should be transparent to messages (or
events to which messages transform) origin and destination
(sans a logical or virtual name). However, unlike the author Colin Clark, I do believe the current crop of vendor products, most notably Progress Apama maintain this separation of the physical from the virtual.
The rationale behind the lack of CEP-based applications in the Cloud
(ok, there's that word again) are found in other factors. To
explain my reasoning I'll start by dividing CEP-based
into two categories. Of course there are many ways to categorize
CEP-based applications, but for the sake of this discussion, I'll use
CEP-based Application Categories
Not sure I could make a simpler layman-like description, but needless to say it
warrants further explanation (or definition in sticking with our theme)
CEP-based applications that do things
In other verticals, an up and coming usage of CEP is
location-based services. This is one that leveraging smart mobile
devices (i.e "don't care where the message is going")
to provide promotions and offers.
CEP-based applications that observe other applications doing things
Of course the demarcation line
between these two classifications is not clear cut. Providing greater
visibility is just a starting point,
monitoring for opportunities to take action is just as important such
as kicking-off a fraud watch if a suspected wash-trade occurred
(so in a sense they are doing things).
Where for art thou oh CEP
When considering the Cloud, an
important point to consider is dependency. Specifically, there is a
dependency that the underlying applications and business processes
exist in the Cloud for (observing) CEP to overlay them. I
that Enterprise business has not yet migrated their key business
processes to the Cloud on a widespread scale just yet. Why not? What
are the barriers? Security, regulatory compliance, DR, investment
costs, limited skill sets are just a few of the challenges mentioned in
article. I suspect these barriers are far reaching, keeping
the pace of Cloud deployment in check to the point where it's not as
yet strategic to many.
One of key things that makes the Cloud a reality is virtualization, it has clearly revolutionized PaaS
as the Cloud. Virtualization does come at a cost, there is
a latency penalty for the convenience, no matter how
small for some use-cases that cost is too great.
Make no mistake, I am certain the Cloud with all it's twenty-one definitions is
the future of computing. It's an imperative that will knock down the
barriers and change the face of the Enterprise and when it reaches
critical mass CEP will be there.
Once again thanks for reading, you can 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 © 2017 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.