The scale is staggering
14 years ago I was running a group at TIBCO that was bringing TIBCO to the Internet. Yahoo!Finance was built on the TIBCO pubsub infrastructure. At the time Yahoo was the biggest cloud/internet company and the finance pages were the most popular pages on the companies web site other than search. The hits were astronomical even at the time. It was the fever time in the tech internet industry and everyone was following the stocks of the new internet players. Many people including myself had written programs that leveraged Yahoo's web site as an API to build applications for stock analytics, portfolio analysis and to embed in their own websites. I know that Yahoo was getting 100 million hits to the web site a day or more but probably few of those were really applications making calls. There weren't a lot of other APIs in the Internet at that time. I would guess that there were 10^9 a billion "pseudo-API calls"/month back then. This is the kind of traffic that a small startup would get today for its API. :)
Event driven computing is the way we build software to give you information instantly when it happens. I invented Publish/Subscribe Event driven computing at TIBCO in the 1980s.
Event driven computing and publish / subscribe (pubsub) is critical to the new world of Cloud, Mobile and now Internet of Things. I will show how publish / subscribe for IoT is very powerful way for IoT devices to interact.
First, I am going to take you on a journey of a little history to get you to the point you understand how event driven architecture led the way to the technology of today and fits into the new world of cloud, mobile, Internet of things and social. I think this has been for me as the creator of publish/subscribe an exciting journey that hasn't ended and seems on the verge of another renaissance as we move to the Connected World of Cloud, Services, APIs, Mobile, IOT.
Accelerating Pace of Change,
Event Driven Architecture,
Event Driven Architecture EDA,
Internet of Things,
Publish / Subscribe,
I could talk about each of these components in isolation, for instance, Mobile and talk about the growth of it and changes it is fostering but you wouldn't get the big picture. The change we are seeing can only be understood by considering all these components together. They each affect each other and the widespread adoption and improvement in each drives the success of the other. Therefore, this article is intended to give you the context to understand the entire change we are undergoing rather than any particular element. By seeing that you see that adopting any one technology or doing any one thing will ultimately fail.
The idea of the virtuous circle is that each component of the circle has been critical to the success of the other parts of the circle. It is hard to imagine the success of any of these elements in isolation. The massive adoption of key aspects of the circle is clearly needed but each element of the circle has been key to the success and adoption of the other parts. The constant improvement in each aspect of the circle drives improvements in other parts of the circle driving more adoption and more innovation. The process feeds itself and grows faster as each element grows. It is impossible to say which element is less - critical so they have to be considered as one.
These components of the virtuous circle imply that to leverage the benefits of the circle you have to be using components of the circle in your processes. The more components you use the more benefit you gain from the circle and the faster the change you will experience. The combination of these technologies is being called Platform 3.0.
The benefits of each part of the virtuous circle
APIs are the honeybee of software (apis is latin for honeybee)
Accelerating Pace of Change,
Faster Time to Market,
InnerSource OpenSource Megatrend SDLC Enterprise R,
open source software,