Overview

This chapter provides an overview of the FS-CD Adapter architecture and the event-driven integration pattern using Kafka, a publish-subscribe messaging broker.

The integration pattern has various benefits over point-to-point integrations between the suite modules and FS-CD:

  • Eventual Consistency: The pattern ensures eventual consistency which guarantees that, given enough time, all systems will eventually reach a consistent state. See Failure Scenarios and Resolution for more about consistency.

  • Loose Coupling: The event-based and asynchronous communication enables loose coupling between systems, allowing them to operate independently.

  • Scalability: Asynchronous message processing with Kafka allows for scalable and distributed processing of events.

  • Improved Responsiveness: Asynchronous processing enables systems to handle requests more quickly, as tasks can be processed in the background.

  • High Availability: Kafka’s distributed architecture and the ability to retry and reprocess messages enhance the overall availability of the system.

  • Stateless: The adapter is stateless and does not require any persistence or database.

Index

  1. Domain Overview
  2. Integration Architecture
  3. Failure Scenarios and Resolution
  4. Module Structure