Event-driven architecture

As explained in Google Anthos in Action

Event-driven architecture is a software architecture in which components communicate and initiate processing through events.

Event-driven architecture coordinates processing through events from internal or external sources. In Knative Eventing, event sources send events to a Broker, Triggers filter and route them, and target Services process them. section 9.3.3

Knative implements the pattern through:

• CRDs and controllers that define and manage event handling. section 9.3.3
• Brokers that receive or pull events as an event mesh. section 9.3.3
• Triggers that filter events and route them to Knative or Kubernetes Services. section 9.3.3
• Pluggable event storage, CloudEvents parsing, automatic scaling, and predefined or custom sources. section 9.3.3

Figure 9.6 Knative Eventing resources

Use the resource diagram to trace event flow from sources through a Broker and Trigger to a Service. section 9.3.3

How Google Anthos in Action covers it

How deep it goes

Explains Brokers, Triggers, sources, storage, scaling, and basic pipelines, while deferring complex event pipelines.

Examples

Uses Broker and Trigger manifests, a Cloud Pub/Sub source, and event flow diagrams as implementation examples.

What you can do after

Operate/configure Knative Eventing pipelines that route events from sources to scalable services.

How it connects

Connects event-driven architecture with Knative Eventing, Kubernetes Services, Knative Serving, CloudEvents, Brokers, and Triggers.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Kafka for ArchitectsAn event-driven system is a software system whose components react to events rather than relying primarily on direct synchronous interactions.
• 

  liveBookmanning.com
  Effective Platform EngineeringEvent architecture is a system design pattern in which components communicate and integrate through emitted and consumed events.
• 

  liveBookmanning.com
  Distributed Machine Learning PatternsA processing architecture in which computation is initiated in response to incoming events or requests.
• 

  liveBookmanning.com
  MongoDB 8.0 in Action, Third EditionAn event-driven application is an application whose components communicate and react through events rather than relying primarily on direct requests for data.
• 

  liveBookmanning.com
  Architecture Modernization: Socio-technical alignment of software, strategy, and structureAn event-driven architecture is a software architecture in which components communicate and initiate processing through events.
• 

  liveBookmanning.com
  AI-Powered Developer: Build software with ChatGPT and CopilotEvent-driven architecture is a software architecture in which components communicate and react through events.
• 

  liveBookmanning.com
  Learn Docker in a Month of Lunches, Second EditionAn event-driven architecture is a software design in which components publish events representing occurrences and other components react to those events.
• 

  liveBookmanning.com
  Apache Kafka in ActionEvent-driven architecture is a software architecture in which components communicate by producing and consuming representations of events.
• 

  liveBookmanning.com
  LatencyEvent-driven concurrency coordinates work by responding to events that signal changes or operation completions rather than blocking execution while waiting.

Compare how 10 books explain event-driven architecture →

Related concepts

• design patternkind of · A design pattern is a reusable, general solution structure for a recurring software design problem in a particular context.
• eventuses · An event is an occurrence, change, or associated record or notification recognized as significant within a system or context.
• Apache Kafkauses · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
• asynchronous programminguses · Asynchronous programming is an execution approach in which operations can progress independently without requiring the initiating flow to wait for their completion or an immediate response.
• message brokeruses · A message broker is intermediary software that receives, routes, and delivers messages between communicating producers and consumers.
• request-response APIcontrasts with · A request-response API is an interaction pattern in which a requester sends a request to a provider and receives a corresponding response.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.