About This Architecture

Event-driven chat application runtime on AWS EKS orchestrates workflows with Temporal and delivers real-time updates via Redis Streams. Public API in Go/Echo triggers Temporal workflows stored in dedicated RDS PostgreSQL, while Temporal Workers execute activities against a separate business RDS database enforcing row-level security. Redis Streams on ElastiCache serves as a lightweight delivery bus pushing events to SSE/WebSocket gateway, enabling sub-second chat message delivery without polling. This architecture demonstrates separation of control plane state (Temporal DB) from domain data (Business DB), a best practice for multi-tenant SaaS platforms requiring audit trails and data isolation. Fork this diagram on Diagrams.so to customize namespace configurations, add Temporal workflow definitions, or explore alternative message buses like Amazon MQ or EventBridge.

People also ask

How do I architect a real-time chat application on AWS EKS using Temporal for workflow orchestration and Redis Streams for event delivery?

Deploy Temporal Frontend, History, and Matching services in a dedicated EKS namespace with RDS PostgreSQL for control plane state. Use Temporal Workers to execute activities against a separate business RDS database. Publish events to ElastiCache Redis Streams, consumed by an SSE/WebSocket gateway for sub-second real-time delivery to end users.