Goodbye SOA (Service Oriented Architecture), Hello EDA (Event Driven Architecture) (or Hype after Hype, after...

It seems that SOA (Service Oriented Architecture) is out, and the new hype is called EDA (Event Driven Architecture). That makes me wonder in what way this will change the world. 71% of the projects fail, a figure that is rather constant over the years. And EDA is going to change this…

The definitions of SOA and EDA

It is inevitable that a hype comes and goes away again. That is a fact of life. It is also fact that many of them are never missed, and some 'Remain in light'. Why not compare SOA and EDA, and see what that brings us. Remember the definition of SOA: A service-oriented architecture (SOA) is a group of services that communicate with each other, through data-passing or by coordinating some activity, and having some means of connection. And the definition of EDA: Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. This definition stresses the technical nature of EDA, referring to the software architecture. From these definitions it follows that SOA is an answer to business issues. SOA is in quite a different league than EDA. It will 'remain in light'.

The merits of EDA

You could ask whether EDA does not have any merits then. Well, that is too bold. Around 1970 James Martin designed the well know Information Engineering methodology. The best addition to that was some 20 years later: Business Event Analysis (BEA). If you are interested I would love to give an interested group of people the BEA training course again. BEA helps business users define a view on how business processes are related: Which event triggers what, and with what expected business result. Very sensible stuff, BEA. If EDA brings this kind of thinking that as well, I am comfortably satisfied with this new hype.

SOA Will remain Light, Will EDA…

Back to my remark regarding the fact that 2 thirds of all projects fail. This is not as significant as it looks like. About 80% of cost goes to maintenance including small changes. Reduction of that amount is therefore much more important than increasing the success factor of projects.

My conclusion if that, even if EDA re-introduces some kind of BEA thinking, it is not going to change the world. It can help new projects. Note there needs to be done a lot of work to be able to use EDA. You will need methods and techniques, tools, trained people, and last but not least an EDA implementation plan. I have all that ready, but I do not think I will need it in the near future. Because I do not think that EDA will be that important to serious companies looking for cost cutting measures…

And you, what do you expect from EDA? Let us discuss.

Undefined

back to top