Presentation: Evolution of a Backend for a Streaming Application

2026-05-11 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure, Operations & Process Management · Depth: Advanced, extended

Summary

Daniele Frasca, an AWS Serverless Community Builder, details the architectural evolution of Joyn, a German streaming service, from fragile single-node setups to resilient serverless architectures on AWS. The presentation, recorded at InfoQ Dev Summit Munich on May 11, 2026, covers strategies for achieving data consistency using patterns like Hub and Spoke and Claim Checking. It also explains how Joyn improved scalability and resiliency through cell-based isolation, multi-layered caching with CloudFront and Momento, and cost-optimization techniques like dynamically shifting traffic between AWS Fargate and Lambda. The goal was to build an affordable, highly available, and scalable multi-region active-active streaming backend for millions of users.

Key takeaway

For MLOps Engineers or CTOs building high-scale, resilient streaming platforms, prioritize serverless AWS services and strategic architectural patterns. Implement cell-based isolation and multi-layered caching to enhance availability and reduce blast radius. Dynamically manage compute resources like Fargate and Lambda to optimize costs, ensuring your infrastructure can gracefully handle traffic spikes and regional failures without human intervention.

Key insights

Serverless architectures and strategic patterns enable scalable, resilient, and cost-effective multi-region streaming applications.

Principles

• Delegate operational complexity to cloud providers.
• Reduce blast radius with cell-based isolation.
• Implement multi-layered caching for performance and cost.

Method

Transition from monolithic to serverless AWS services, employing Hub and Spoke for data consistency, cell-based architecture for isolation, and dynamic traffic shifting between Fargate and Lambda for cost-effective scalability.

In practice

• Use EventBridge Pipe for data validation and transformation.
• Shift traffic between Fargate and Lambda based on load.
• Apply cell-based architecture for localized deployments.

Topics

• AWS Serverless Architecture
• Streaming Application Backend
• Data Consistency Patterns
• Multi-Region Architecture
• Cost Optimization Strategies

Best for: MLOps Engineer, CTO, VP of Engineering/Data, Software Engineer, DevOps Engineer, AI Architect

Related on AIssential

• The Evolution of Data Engineering: How Serverless Compute is Transforming Notebooks, Lakeflow Jobs, and Spark Declarative Pipelines — Databricks serverless compute automates infrastructure management, offering significant cost savings and performance improvements.
• Coinbase Postmortem Reveals How a Localized AWS Failure Triggered a Multi-Hour Trading Outage — Outages often stem from unexpected interactions between individually manageable failures and architectural assumptions.
• EP196: Cloud Load Balancer Cheat Sheet — Cloud-native architectures enhance scalability and efficiency through specialized components like load balancers, CQRS, Docker, and serverless functions.
• Netflix Serves 84% of Query Results from Cache with Interval-Aware Caching in Apache Druid — Decomposing query results into time-aligned segments enables high cache reuse for rolling window analytics.
• Scaling on Demand: How Serverless Architectures Empower Agile and High-Performing Platforms — Serverless architecture offers macOS developers scalable, cost-efficient, and maintenance-free application development.
• Optimizing cloud economics with linear elastic caching — Dynamic, cost-aware cache sizing using a "ski rental" model significantly reduces total ownership cost by optimizing memory use.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.