Abstract: Event-driven architectures have been around for a long time, but new trends and innovations in "serverless" computing, data streaming, and Agile practices have created the ground for an evolutionary step that will have significant impact on the way we design and build software over the next decade or more. Much like APIs drove a revolution in public services for RPC, REST, and similar "pull" use cases across organization boundaries, the market now promises to similarly define standard mechanisms to enable "push" notifications of discrete data and activities. This practice, which we call Flow, will drive a revolution in interconnectivity similar to what we saw with HTML and REST.
Agile is central to the success of these mechanisms, and is one of the key reasons why this will happen sooner rather than later. The ability to adapt quickly to customer needs, combined with the ability to react quickly to new and changing event sources, is required to make event-driven practices work. In this talk, James Urquhart will describe the changes on our horizon, discuss existing architectures, mechanisms and organizations that are leading the way, and talk specifically about how Agile teams are well prepared to both drive and benefit from Flow systems. The talk is targeted at technology, development, and product leaders who wish to understand how Flow fits into their architecture portfolio.
Learning Outcomes: - Get a clear definition of what Flow is, who is pioneering Flow approaches, and specific technologies and open source initiatives that are driving the future.
