Event-Driven Architectures: Orchestrating Cloud Native Workflows

A Conf42 Cloud Native 2024 session focused on practical event-driven architecture patterns, workflow orchestration with Step Functions, and design guidance for resilient cloud-native systems.

#AWS#EventBridge#Step Functions#Serverless
Conf42 Cloud Native 2024 slide for Event-Driven Architectures session

Topic: Designing scalable cloud-native systems with event-driven patterns, choreography, and orchestration

Target audience: Cloud Architects, Backend Engineers, DevOps and Platform Teams

Location: Conf42 Cloud Native 2024 (Online)

Related stack: AWS, EventBridge, Step Functions, Serverless

Event link: https://www.conf42.com/Cloud_Native_2024_Md_Mostafa_Al_Mahmud_eventdriven_architectures_orchestrating

Abstract

Unlock the power of event-driven architectures in the cloud through seamless workflow orchestration, modern cloud-native patterns, and practical strategies for building scalable and resilient systems.

Session summary

This session explains why modern applications are naturally event-driven and how placing events at the center of architecture enables:

  • Independent feature development.
  • Easier cross-service integration.
  • Loose coupling and modularity.
  • Better scalability and adaptability.

It walks through choreography and orchestration as complementary communication models for distributed systems, and explains when to use each model or combine both in real-world designs.

The talk also highlights bounded contexts from domain-driven design, event-streaming patterns, and reliability fundamentals such as idempotency and event ordering for consistent operations.

Practical architecture guidance

A major implementation focus is Step Functions with EventBridge for low-code, loosely coupled workflow integration, including KYC-style process modeling and decision-driven orchestration paths.

Key practical points include:

  • Choosing Standard vs Express Step Functions based on workload behavior.
  • Integrating human-in-the-loop decision points where needed.
  • Using Map states for parallel item processing.
  • Applying event storming and shared language practices during design.

Why this matters

By combining choreography and orchestration intentionally, teams can build cloud-native systems that are robust, scalable, and easier to evolve over time.