ie8 fix
madison

Goodbye real-time era, hello 'event-driven' era

By | May 6, 2008, 7:55am PDT

Summary: A bank may deal with 100 million events a month, but few are leveraged and tied to information in databases

If banks are so smart with their terabytes’ worth of customer information, why do you have to keep reminding them what language you speak every time you interact with them?

100 million events a month, but few are tied to data in databases

Speaking at the recent TUCON conference held in San Francisco, Tibco CEO Vivek Ranadivé observed that we are moving out of what he called the “Database Era,” in which software is tied to databases — and are moving into the “Event Driven Era,” in which data is tied to transactions across the network. (Ranadivé is also author of The Power of Now and The Power to Predict.)

It’s not a moment too soon to change eras, as Ranadivé referred to database-based architecture as “extortionist architecture.” Information can no longer be locked away in data silos, he said.

Look at the example of a typical large bank, he illustrated. Such an institution deals with “100 million events a month.” Yet, few of these events are actually captured and linked to the accumulated intelligence on the back end. Ranadivé pointed out that when he goes to an ATM, the first question he is asked is whether he wants to conduct the transaction in English or Spanish. “All this infrastructure, and the bank doesn’t know that I use English, even though I’ve gone to their ATMs zillions of times,” he said.

So there’s plenty of work cut out for us in the Event Driven era. Look at the massive digital infrastructures built up in enterprises these days.“Your average Fortune 500 company has more back-end infratsructure than the entire Internet,” he pointed out.

That’s why the time is ripe for organizations need to move to Event Driven Architecture — in which “hundreds of terabytes of information on the back end are tied to events at the moment of truth,” Ranadivé said. What organizations are seeing is an “event cloud” that needs to be linked to data stores and processes. Not only will organizations be able to transact with customers with a wealth of historical and real-time data, but also predict future actions or trends.

The Event Driven Architecture moves organizations beyond real time, “which is still reactive in nature,” he said. “We have to go beyond real-time and be event driven,” Ranadivé said. This requires a shift — which is underway — away from the traditional “extortionist architecture” database to a service oriented architecture.

(My colleagues Dana Gardner and Tony Baer also provide context to Ranadivé’s remarks and the overall Tibco conference.)

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Joe McKendrick is an author, consultant and speaker specializing in trends and developments shaping the technology industry.

Disclosure

Joe McKendrick

Joe McKendrick is an independent consultant, editor and speaker.

Joe has performed project work (white papers, articles, blogs, research and presentations) for the following companies in the IT marketspace:

  • CBS Interactive/CNET/ZDNet (this blog)
  • ebizQ
  • Evans Data
  • Gartner
  • IBM
  • Informatica
  • IDC
  • Microsoft
  • Systinet/HP
  • Teradata
  • Unisphere Reseach, a division of Information Today, Inc.
  • WebLayers

Joe has also performed research work for the following sponsoring organizations in partnership with Unisphere Research, a division of Information Today, Inc.

  • IBM
  • Luminex
  • Noetix
  • Oracle Corp.
  • Teradata
  • Informatica
  • International Oracle Users Group
  • Oracle Applications Users Group
  • Professional Association for SQL Server
  • International DB2 Users Group
  • International Sybase Users Group
  • SHARE (IBM large systems users group)

Biography

Joe McKendrick

Joe McKendrick is an author and independent analyst who tracks the impact of information technology on management and markets. Joe is co-author, along with 16 leading industry leaders and thinkers, of the SOA Manifesto, which outlines the values and guiding principles of service orientation. He also speaks frequently on Enterprise 2.0 and SOA topics at industry events and Webcasts, and serves on the program committee for this year's SOA & Cloud Symposium in London. As an independent analyst, he has also authored numerous research reports in partnership with Unisphere Research, a division of Information Today, Inc. for user groups such as SHARE, Oracle Applications Users Group, and International DB2 Users Group. In a previous life, Joe served as director of the Administrative Management Society (AMS), an international professional association dedicated to advancing knowledge within the IT and business management fields. He is a graduate of Temple University.

Related Discussions on TechRepublic

Did you know you can take part in these discussions with your ZDNet membership?
15
Comments

Join the conversation!

Just In

Event-Driven Architecture ...
brutallyfrank 10th Oct 2008
is nothing new, it's a real-time embedded development concept -- how do you think alarm systems work under the hood?

When a sensor detects something -- it's an event.

You SOA web developers need to stop drinking all that kool-aid.
0 Votes
+ -
This all sounds very whiz-bang...
johnay 6th May 2008
...but I think I would prefer my financial information be "locked in a silo."

Also, "transaction" is a noun. "Transact" is the verb you seek.
0 Votes
+ -
Contributr
Thanks!
Joe McKendrick 6th May 2008
Correction made!
0 Votes
+ -
It's not whiz-bang and it's not new
reamon@... 6th May 2008
Ranadive and others (META Group back in the day), have been promoting the notion of the event-driven enterprise for over a decade.

I'm not exactly sure what is meant by "beyond real-time." Event-driven solutions typically are not real-time but are usually "near" real-time.

IMO, EDA and SOA are orthogonal notions. One doesn't subsume the other. A business or enterprise architecture is likely to adopt (should adopt?) principles from both approaches.
0 Votes
+ -
Er, '"event cloud? that needs to be linked to data stores and processes'" still sounds like database storage to me.

This is hardly new? EJB anyone? OOP? Ever do a servlet, or do listeners?

I don't see how a large corporation could 'eliminate' the need for storage; and maybe using a financial corporation is a terrible example..

Call it what you want, but when you press the 'withdraw' button on that ATM, event-fired or not, it's gotta go to your account and deduct the cash. And if the system crashed at that point, the record must still be updated; usually done by database storage.
0 Votes
+ -
Errr
fr0thy2 6th May 2008
memory resident versus disk resident
0 Votes
+ -
I think it means...
Anton Philidor 6th May 2008
... combining available information to make worthwhile reports. An amazing innovation awaiting only the first company to make use of it for the concept to explode. Soon everyone will be receiving hundreds of reports and wondering what life was like previously.
0 Votes
+ -
LOL +1 (NT)
Erik Engbrecht 6th May 2008
.
100 million a month is hardly a large bank. Besides, most of these events will be transactions that are typically still processed in batch, resulting in peak loads of millions transactions per hour. If all these transactions can be considered events, that will result in peaks up to 1000 events per second. Considering the idea in your post that in the event driven era the main goal is to share the information, one should expect that one event will result in a few processing actions per event. So the hardware you will need for this will be impressive.

Legal issues might make up for another interesting aspect. Not every part of an organisation will be granted access to the information that is in the events. And the more the organisation depends on 'event driven', the harder it will get to control the access rights without losing flexibility.

Nevertheless, i think you are right. At least, a more event driven approach will add value to the service catalog organisations have in place right now. Just don't expect the change to happen overnight.
0 Votes
+ -
Contributr
Great point on legal aspects...
Joe McKendrick 6th May 2008
Banks are heavily regulated; others also have SOX and other mandates that require heightened data protection and auditability. This is likely an area that will be tested in the years to come.
0 Votes
+ -
Ranadive sounds a bit of a dreamer.
peter_erskine@... 7th May 2008
Information about the customer isn't going to come out of thin air. Information isn't abstract. Ranadive's thinking is. I think he needs to sit down with a copy of Freemind and come up with some actual tangible proposals.
0 Votes
+ -
Ranadive is TIBCO
reamon@... 8th May 2008
He has become quite wealthy with his tangible proposals! TIBCO is still a leading provider of event-oriented software tools. The big success story in "The Power of Now" was in the financial services industry where TIB (The Information Bus--the TIB in TIBCO) made a name for itself.

I agree that his notion of databases being "extortionist" is a bit extreme. His ATM example is off--you can publish all the "Ranadive speaks English" events that you want but it won't help for next time if you don't store it somewhere!

That said, his point is more about getting information and events distributed more easily and readily. Unfortunately that message gets lost in the DB bashing.
0 Votes
+ -
"data is tied to transactions across the network"

Or alternatively on a tape, or a stack of cards, or in your e-mail.

I have studiously avoided TIBCO products and will continue to do so on the basis of this pronouncement.

Depressing that someone can make so much money selling such outmoded ideas as something new. However this is not untypical in the industry, Oracle "Advanced Queueing" is also batch processing dressed up in fancy new terminology.

Fortunately, every prediction in the last twenty years that the RDBMS is about to disappear has proved to be completely false. Codd got it right, let's try and persuade the vendors to implement his ideas properly (SQL != Relational). In the relational model you represent "events" in the same way as you represent every other kind of data (which is a problem if you are vendor trying to sell some "new" product - but a great advantage for customers).
There is of course no set of absolutes. Sometimes you want events to be broadcast to appropriate listeners (for reasons that are quite unpredictable at application design time) and sometimes you don't. Eventually the data are going to be "locked up in a databsae somewhere", but on their journey to that safe house, many things may need to happen to them. Sometimes it is just census (how many did we have), at other times we need to be able to catch fraud.

Here's a short posting that looks at some differences:

http://businessanditarchitecture.blogspot.com/

Disclosure - yes I wrote that article......
0 Votes
+ -
Not bad, but be careful....
reamon@... 12th May 2008
...about generalizations that could be misconstrued.

"So here, we have a much lighter weight, less surly architecture an approach where the actions are distinguished from the notifications, where the actors are actively listening and making decisions for themselves. An architecture that exhibits autonomy and a loosely coupled style."

"Much lighter weight?" How can something that will likely use yet another component (message broker) be more light weight than a point-to-point request/response? I'm not sure lighter weight is an accurate selling point.

Whilst publishing events may seem to make for a chatty infrastructure, typically publishers are not built to publish things that noone is listening for. That makes the build up of the system a drawn out process as new needs require a revisit to the publishers to start publishing the newly desired data.

Lastly, it is the relatively rare business integration that doesn't care about a message getting to where it is supposed to be (fire and forget). "...but it is absolutely impossible for the originator or broadcaster of the information to control what happens to it." Often, the source system *must* control exactly what happens. One of the reasons the request/response is so popular is because the source application *must* know that the message was delivered. Replicating this capability on an async messaging infrastructure adds all kinds of complexity.

You're absolutely right that one must apply SO and event-driven principles in the right places. Just be careful about characterizing event-driven approaches as more "capable" or more desirable. It is a different interaction style that has its place, but designers need to be aware to not over do it, IMO.
0 Votes
+ -
Event-Driven Architecture ...
brutallyfrank 10th Oct 2008
is nothing new, it's a real-time embedded development concept -- how do you think alarm systems work under the hood?

When a sensor detects something -- it's an event.

You SOA web developers need to stop drinking all that kool-aid.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix
Click Here
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix