0%

Book Description

Dominated by streaming data and events, the next generation of software development 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 the critical implications of that evolution: What happens when event and data stream standards 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 Pivotal Cloud Foundry, guides enterprise architects, software developers, and product managers through:

  • The business imperative for flow
  • Why worldwide flow is likely to happen
  • The factors that will enable flow in next 5–10 years
  • What you can do to take advantage of worldwide flow as it evolves
  • A Wardley map exploration that shows why worldwide flow is predictable

Table of Contents

  1. 1. Introduction
    1. What is Flow?
      1. Flow and Integration
      2. Flow and Event-Driven Architectures
      3. The Ancestors of flow
      4. Code and Flow
      5. The Chapters Ahead
  2. 2. The Business Case for Flow
    1. Drivers for Flow Adoption
      1. Improving Customer Experience
      2. Improved Organizational Efficiency
      3. Innovation and Experimentation
    2. Enablers of Flow Adoption
      1. Lowering the cost of stream processing
      2. Increasing the Flexibility of Data Flow Design
      3. Creating the Great Flow Ecosystem
    3. What Businesses will Require from Flow
    4. The Effects of Flow Adoption
      1. Expanding the Use of Timely Data
      2. The Importance (and Peril) of Flow Networks
      3. Flow’s Impact on Jobs and Expertise
      4. Flow and New Business and Institutional Models
      5. Flow and Scale
  3. 3. Understanding the Flow Value Chain
    1. Recap: The High Level Properties for Flow
    2. Wardley Mapping
    3. Finding a Purpose
    4. Mapping a Landscape
      1. What is a Map?
      2. Mapping Technology
    5. Defining our Scope
    6. Defining our Users and User Need
    7. Defining our First Components
    8. Adding Components Required to Make Streams Valuable
    9. The Final Piece
    10. Promise Theory
      1. What is Promise Theory?
      2. Promise Theory Notation
      3. Using Promise Theory to Identify Opportunity
      4. Delegation and Conditional Promises
      5. Combining Promise Theory and Flow
    11. Have Models, Will Travel
  4. 4. Evaluating The Current Streaming Market
    1. Service Buses and Message Queues
      1. Mapping Service Busses and Message Queues
    2. Internet of Things
      1. MQTT
      2. HTTP and WebSocket
      3. Mapping Internet of Things Architectures
    3. Event Processing
      1. Functions, Low-Code, and No-Code processors
      2. Log-based Stream Processing Platforms
      3. Stateful Stream Processing
      4. Mapping Event Processing Platforms
    4. Streaming Architectures and Integration Today
18.220.13.70