Flow Architectures: An Introduction
Download as PPTX, PDF0 likes534 views
The document introduces the concept of 'flow' as event-driven integration across organizational boundaries through standardized interfaces and protocols. It highlights the benefits of flow, including lower integration costs, increased flexibility, and improved customer experience and productivity. The document also touches on the importance of understanding basic patterns and use cases related to flow architectures.
Flow Architectures: An Introduction
- 1. Flow Architectures: An Introduction James Urquhart Principal Technologist, VMware
- 5. What is “Flow”? Event-Driven Integration Across Organization Boundaries Through Standard Interfaces and Protocols flow?
- 6. Consumers (or their agents) request connections to producer streams through standard self- service interfaces. What is “Flow”? Event-Driven Integration Across Organization Boundaries Through Standard Interfaces and Protocols
- 7. Producers (or their agents) chose which requests to accept or reject. What is “Flow”? Event-Driven Integration Across Organization Boundaries Through Standard Interfaces and Protocols
- 8. Consumers (or their agents) do not need to actively request data— events are pushed to them as they are available. What is “Flow”? Event-Driven Integration Across Organization Boundaries Through Standard Interfaces and Protocols
- 9. Producers (or their agents) maintain control of what events are transmitted to whom, when. What is “Flow”? Event-Driven Integration Across Organization Boundaries Through Standard Interfaces and Protocols
- 10. Events are transmitted over the network using standard protocols, including to-be- determined protocols specifically designed for flow mechanics. What is “Flow”? Event-Driven Integration Across Organization Boundaries Through Standard Interfaces and Protocols
- 13. Sounds like PubSub… HTTP + WebSocket (for example) would qualify, if the other conditions are met.
- 15. What Flow Enables A lower cost of integration (standard interfaces and protocols)
- 16. What Flow Enables Increased flexibility (composable solutions)
- 17. What Flow Enables A rich solution ecosystem (interoperable data flows)
- 18. Why would anyone want event-driven integration? Customer experience (keeps context real-time)
- 19. Why would anyone want event-driven integration? Employee productivity (reduces LT and PT)
- 20. Why would anyone want event-driven integration? Business innovation (enables experimentation)
- 22. First
- 23. “Flow without interaction is just shoving bits around for no good reason.” - me
- 24. Flow Value Chain Arrange the users and needs into a graph, with the items more visible to the users at the top of the page, and those least visible at the bottom.
- 25. Flow Value Chain How do we know this is right?!?
- 26. Promise Theory Examples of promises between Flow Integration needs. Specifically, there are promises between the components that interact with the streams. From Flow Architectures: The Future of Streaming and Event-Driven Integration
- 29. Today’s Technologies Fall Right Into Place… From Chapter 4 of Flow Architectures: The Future of Streaming and Event-Driven Architectures
- 30. Today’s Technologies Fall Right Into Place… From Chapter 4 of Flow Architectures: The Future of Streaming and Event-Driven Architectures …but they aren’t flow yet.
- 32. Gameplay
- 33. Gameplay
- 34. Gameplay
- 37. Understand Use Cases Addressing and Discovery Command and Control Query and Observability Telemetry and Analytics
- 39. Get involved! (And buy my book. 😉)