Muutke küpsiste eelistusi

Flow Architectures: The Future of Streaming and Event-Driven Integration [Pehme köide]

  • Formaat: Paperback / softback, 250 pages, kõrgus x laius: 233x178 mm
  • Ilmumisaeg: 31-Jan-2021
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1492075892
  • ISBN-13: 9781492075899
Teised raamatud teemal:
  • Pehme köide
  • Hind: 54,01 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Tavahind: 63,54 €
  • Säästad 15%
  • Raamatu kohalejõudmiseks kirjastusest kulub orienteeruvalt 2-4 nädalat
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Tellimisaeg 2-4 nädalat
  • Lisa soovinimekirja
  • Formaat: Paperback / softback, 250 pages, kõrgus x laius: 233x178 mm
  • Ilmumisaeg: 31-Jan-2021
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1492075892
  • ISBN-13: 9781492075899
Teised raamatud teemal:

Software development today is embracing events and streaming data, which optimizes not only how technology interacts but also how businesses integrate with one another to meet customer needs. This phenomenon, called flow, consists of patterns and standards that determine which activity and related data is communicated between parties over the internet.

This book explores critical implications of that evolution: What happens when events and data streams help you discover new activity sources to enhance existing businesses or drive new markets? What technologies and architectural patterns can position your company for opportunities enabled by flow? James Urquhart, global field CTO at VMware, guides enterprise architects, software developers, and product managers through the process.

  • Learn the benefits of flow dynamics when businesses, governments, and other institutions integrate via events and data streams
  • Understand the value chain for flow integration through Wardley mapping visualization and promise theory modeling
  • Walk through basic concepts behind today's event-driven systems marketplace
  • Learn how today's integration patterns will influence the real-time events flow in the future
  • Explore why companies should architect and build software today to take advantage of flow in coming years
Foreword ix
Preface xi
The 10-Year Impact of the World Wide Flow xvii
1 Introduction To Flow
1(16)
What Is Flow?
3(3)
Flow and Integration
6(3)
Flow and Event-Driven Architectures
9(3)
The Ancestors of Flow
12(1)
Code and Flow
13(2)
The
Chapters Ahead
15(2)
2 The Business Case For Flow
17(28)
Drivers for Flow Adoption
18(8)
Improving Customer Experience
18(2)
Improved Organizational Efficiency
20(4)
Innovation and Experimentation
24(2)
Enablers of Flow Adoption
26(10)
Lowering the Cost of Stream Processing
26(3)
Increasing the Flexibility of Data Flow Design
29(4)
Creating the Great Flow Ecosystem
33(3)
What Businesses Will Require from Flow
36(1)
The Effects of Flow Adoption
37(7)
Expanding the Use of Timely Data
37(1)
The Importance (and Peril) of Flow Networks
38(2)
Flow's Impact on Jobs and Expertise
40(1)
Flow and New Business and Institutional Models
41(2)
Flow and Scale
43(1)
Next Steps
44(1)
3 Understanding The Flow Value Chain
45(28)
Recap: The High-Level Properties for Flow
45(1)
Wardley Mapping and Promise Theory
46(5)
Wardley Mapping
47(1)
Promise Theory
48(3)
Building a Flow Integration Value Chain
51(10)
Establishing a Scope for the Map
51(1)
Establishing Our Users and User Need
52(1)
Flow Integration Components
53(3)
Interaction Components
56(4)
The Final Piece
60(1)
Mapping Our Value Chain
61(12)
Determining a Measure of Technology Evolution
61(4)
Turning Our Value Chain into a Map
65(5)
Our Final Model and Next Steps
70(3)
4 Evaluating The Current Streaming Market
73(20)
Service Buses and Message Queues
74(4)
Message Queues
75(1)
Service Buses
76(1)
Mapping Service Buses and Message Queues
77(1)
Internet of Things
78(5)
MQTT
79(2)
HTTP and WebSocket
81(1)
Mapping Internet of Things Architectures
82(1)
Event Processing
83(6)
Functions, Low-Code, and No-Code Processors
84(1)
Log-Based Stream Processing Platforms
85(2)
Stateful Stream Processing
87(1)
Mapping Event Processing Platforms
88(1)
Streaming Architectures and Integration Today
89(2)
Next Steps
91(2)
5 Evaluating The Emergence Of Flow
93(42)
Mapping the Evolution to Flow
94(3)
Gameplay
97(5)
Market: Standards Game
98(1)
Accelerators: Exploiting Network Effects
99(1)
Ecosystem: Cocreation
100(1)
The Others
101(1)
Inertia
102(6)
Vendor Inertia
102(2)
Enterprise Inertia
104(1)
Here Be Dragons
105(3)
Flow Requirements, Challenges, and Opportunities
108(20)
Security
108(5)
Agility
113(3)
Timeliness
116(4)
Manageability
120(5)
Memory
125(1)
Control of Intellectual Property
126(2)
Flow Pattern Challenges and Opportunities
128(5)
The Collector Pattern
128(1)
The Distributor Pattern
129(1)
The Signal Pattern
130(2)
The Facilitator Pattern
132(1)
The Unexpected
133(2)
6 Building For A Flow Future
135(36)
Identifying Flow in Your Business
136(15)
Flow Use Cases
137(11)
Modeling Flow
148(3)
"Event-First" Use Cases for Flow
151(11)
Messaging Versus Eventing
153(3)
Discrete Events Versus Event Series
156(3)
Single Actions Versus Workflows
159(3)
Driving Flow Forward
162(8)
Driving Technology Development
162(4)
Driving Flow Networks
166(4)
We Will Make Flow Happen
170(1)
Appendix. Evaluating the Current Flow Market 171(48)
Index 219
James Urquhart is a Global Field CTO at Pivotal Cloud Foundry. Named one of the ten most influential people in cloud computing by both the MIT Technology Review and the Huffington Post, and a former contributing author to GigaOm and CNET, Mr. Urquhart is a technologist and executive with a deep understanding of disruptive technologies and the business opportunities they afford.

Mr. Urquhart brings over 25 years of experience in distributed systems development and deployment, focusing on software as a complex adaptive system, cloud native applications and platforms, and automation. Prior to joining Pivotal, Mr. Urquhart held leadership roles at AWS, SOASTA, Dell, Cisco, Cassatt, Sun and Forte Software.

Mr. Urquhart graduated from Macalester College with a Bachelor of Arts in Mathematics and Physics.