About This Architecture

Event-driven FAQ runtime combining Temporal workflow orchestration with Redis Streams for real-time delivery on Amazon EKS. Temporal Server manages workflow state, retry logic, and task dispatch to FAQ workers, while ElastiCache Redis Streams acts as a short-lived delivery bus publishing run events (queued, running, clarify, answer, escalate, failed, done) to a Realtime Gateway serving SSE/WebSocket clients. Business logic reads from RDS PostgreSQL with row-level security via etla_app role, maintaining separation between Temporal's control plane database and the business domain database. This test-minimum architecture demonstrates how to decouple durable workflow orchestration from ephemeral event delivery, enabling reliable FAQ processing with real-time user feedback. Fork this diagram on Diagrams.so to customize namespace topology, add multi-region failover, or integrate your own Temporal activities and Redis consumer groups.

People also ask

How do I architect a Temporal workflow system with Redis Streams for real-time event delivery on AWS EKS?

Deploy Temporal Server in a dedicated EKS namespace to orchestrate FAQ workflows, use ElastiCache Redis Streams as a short-lived delivery bus for run events, and maintain separate RDS PostgreSQL instances for Temporal state and business data. This diagram shows namespace isolation, worker task dispatch, and SSE/WebSocket real-time push via a gateway consuming Redis Streams.