Presenting Event-Driven Architecture Use Cases

Objectives

After completing this lesson, you will be able to:

  • Describe different use cases for an event-driven architecture
  • Explain blueprints for an event-driven architecture

Overview of Use Cases of an Event-Driven Architecture

Event-driven architecture use cases are crucial because they highlight real-world applications of this technological strategy. Understanding specific use cases reveals how this architecture is crucial for services that require real-time operations, high responsiveness, and asynchronous communication. From financial sector transactions to IoT devices, EDA improves speed, decouples dependencies, and enables scalability. Thus, reviewing different use cases significantly enhances understanding of EDA's benefits and its role in tackling contemporary tech challenges.

In general, use cases of EDA can be classified into four central categories:

The figure illustrates the four categories of event-driven use-cases: decoupling, real-time and hyperautomation, PubSub Style integration, and breaking down silos and cross vendor boundaries.

The frontrunner industries for event-driven architectures are retail, travel, and pharma. This is due to the fact that they are highly distributed both in respect to supply chains and sales channels. Also, the real-time aspect here is highly important.

However, very successful use cases have also been seen in industries like telecommunications, high tech consumer goods, information technology, and food and beverage.

Let’s have a look at five selected event-driven use cases from these front-runner industries, and check out to which use case categories each of them belong.

Use Case 1: Event-Based HR Integration

Topic

Event-driven HR integration scenario combining SAP Integration Suite, advanced event mesh and SAP Integration Suite.

Use Case Categories

Decoupling, Real Time and Hyperautomation

Situation & Goals
  • Integrate SAP-based HR business processes with non-SAP SaaS applications.
  • Stick to SAP SuccessFactors standard approaches in a loosely coupled way.
  • Automated creation of new employee and enrichment of employee data across multiple HR systems including third-party HR systems.
Benefits
  • Re-use of SAP SuccessFactors Solutions Intelligent Services Events allows to stay very close to the standard.
  • Straightforward integration with third-party applications extended by the features of SAP Integration Suite.
  • Competitive advantage in today’s tight labor market to attract talent.
Implementation

Employ modern integration styles combining event-driven and API-based Integration to enrich employee onboarding.

Logical flow of use-case 1.

Use Case 2: Shock Absorber

Topic

Event-driven SAP Integration Suite, advanced event mesh-based scenario buffering extreme peak loads.

Use Case Categories
Situation & Goals
  • When releasing new products or during promotions (for example, Black Friday) the number of concurrent orders via both web shop and stores skyrocket.
  • The extreme amount of concurrent orders cannot be handled using synchronous approaches​.
  • Using synchronous approaches would challenge back-end systems and might lead to significant problems (non-reactive web shop and back-ends, data loss) and/or higher costs (larger back-ends).
Benefits
  • SAP Integration Suite, advanced event mesh buffers extreme peak loads with ease.
  • Web shop stays reactive.
  • Back-ends are shielded from high load.
  • Brokers can be started up for specific time frames.
Implementation
Logical flow of use-case 2.

Use Case 3: Across Vendor Event Mesh

Topic

Collection and aggregation of events from different event sources and event brokers to feed into SAP S/4HANA.

Use Case Categories
Break Down Silos and Cross Vendor Boundaries, Real Time and Hyperautomation
Situation & Goals
  • Order management data of local markets is stored and analysed in separate, localized IT environments.
  • Latency of more than 24 hours to add local market data to central, across-country SAP S/4HANA.
  • Several aggregation steps lead to redundancy and higher costs.
Benefits
  • Order management data is added to central SAP S/4HANA environment in real time.
  • SAP Integration Suite, advanced event mesh glues together several sub-meshes based on Kafka and Azure-based event brokers.
  • Reduction in aggregation steps lead to major cost reduction.
  • Perfect mix of desired localization while having full visibility on a global level.
Implementation
Logical flow of use-case 3.

Use Case 4: Master Data Distribution

Topic

Integration of SAP Master Data Governance with several SAP and non-SAP systems.

Use Case Categories
Decoupling

Note

This use case has won an SAP innovation award. For more information click:

Situation & Goals
  • SAP Master Data Governance central hub for Master Data Management.
  • Asynchronous, loosely coupled rather than transactional integration to decouple dependencies.
  • Push approach to several applications with control over changes preferred.
Benefits
  • Advanced Event Mesh allows for combining push SAP MDG mechanism with Pull mechanism of target systems.
  • Complete decoupling of MDG development from target system developments, with additional buffering if needed.
  • Standard interface definitions, processing and monitoring for all targets.
Implementation
Logical flow of use-case 4.

Use Case 5: Transforming Distributor

Topic

Distribute data from and to highly diverse back-ends including event transformation.

Use Case Categories
Situation & Goals
  • Large number of different back-ends.
  • SAP S/4HANA is leading system.
  • Inbound and Outbound consolidation of data from and to SAP S/4HANA.
  • Due to different back-ends and data formats, a transformation is required
Benefits
  • Data distributed in highly diverse environment in real time (SAP S/4HANA, SAP ECC, SAP ByDesign).
  • Buffering of extreme peak loads.
Implementation
Inbound:
Logical flow of use-case 5, inbound.

Outbound:

Logical flow of use-case 5, outbound.

Event-Driven Architecture Blueprints

Event-driven architecture blueprints are highly important as they provide a clear framework for designing and implementing systems that respond in real-time to business events or changes in the operational environment. These blueprints enable the building of scalable, flexible, and adaptable systems that can easily accommodate increasing data volumes and complex processing logic. Moreover, they promote decoupling, which allows individual components to evolve independently, resulting in increased speed and efficiency.

So, let’s take a look at five event-driven architecture blueprints in conjunction with their main characteristics.

Blueprint 1: Master Data Distribution

Distributing master data to SAP and non-SAP applications.

Main characteristics:

  • Real-time updates for master data.
  • Push/Subscription-based approach.
The figure illustrates the process of the master data distribution.

Blueprint 2: Transforming Distributor

Combining event-driven integration with SAP Integration Suite for event mediation.

Main characteristics:

  • No polling needed.
  • SAP Integration Suite leveraged for enrichment and event transformation.
The figure illustrates the process of the transforming distributor.

Blueprint 3: Real Time Notifications

Employ modern integration styles combining event-driven and API-based integration.

Main characteristics:

  • Small event containing absolutely needed data.
  • Additional API-based data access protected by back-end-side authentication and authorization checks.
The figure illustrates the process of real-time notifications.

Blueprint 4: Across Vendor Mesh

Collection and aggregation of events from different event sources and event brokers

Main characteristics:

  • Diverse event sources and different consumers.
  • Event mediation leveraging SAP Integration Suite.
The figure illustrates the process across vendor mesh.

Blueprint 5: Shock Absorber

Event-driven SAP Integration Suite, advanced event mesh-based scenario buffering extreme peak loads.

Main characteristics:

  • Buffering and decoupling.
  • Cross vendor boundaries.
The figure illustrates the process shock absorber.

Summing Up

In summary, the use cases for an event-driven architecture (EDA) you looked at in this lesson, include telecommunications, high tech consumer goods, retail, information technology, and food and beverage industries. These use cases involve scenarios such as HR integration, shock absorption, event aggregation, master data distribution, and distributor transformation. EDA blueprints are also important and include designs for master data distribution, transforming distributors, real-time notifications, across vendor mesh, and shock absorbers. These blueprints provide a framework for designing and implementing scalable, flexible, and decoupled systems that respond to real-time events.

Log in to track your progress & complete quizzes