Event-driven Architecture
Implement scalable event-driven applications without taking a dependency on specific SDKs, understanding the complexity of Kafka, RabbitMQ, AWS SQS/SNS or any message broker infrastructure and manage less code.
Catalyst provides a unified messaging API with reliability, routing, and broker abstraction built-in, so you can focus on application logic instead of managing event infrastructure, making your code simpler, portable across clouds and future proof to infrastructure changes.
Event-Driven Applications
Event-driven messaging enables producers to publish events without needing to know who consumes them, creating a naturally decoupled system where services can evolve and deploy independently. This separation allows consumers to scale on their own timelines, absorb sudden spikes in workload, and shed load gracefully without impacting upstream systems. Catalyst’s Dapr Pub/Sub API offers a simple way to build asynchronous, event-driven applications without brining the broker semantics into the applications.
Key capabilities:
- Asynchronous communication - Avoid blocking calls and process work without requiring immediate responses.
- Loose coupling between services - Producers and consumers evolve independently without direct lifecycle dependencies.
- Pull and push models - Choose between pull-based or push-based delivery depending on your consumption pattern.
- Interoperability between systems - Integrate cross languages, cloud services, and legacy systems through events.
- Bulk operations - Send or receive multiple messages in a single request for higher throughput.
- Secure messaging - Enforce access control on topics so only authorized applications may publish or subscribe.
Guaranteed Message Delivery
Catalyst provides at-least-once message delivery to ensure events are never lost, even during network issues, restarts, or downstream failures. Combined with built-in resiliency policies and dead-letter queues, Catalyst delivers a reliable, fault-tolerant messaging layer across all supported brokers and infrastructure environments.
Key capabilities:
- At-least-once delivery - Messages are retried automatically and not lost during failures.
- Dead-lettering - Route failed messages to dedicated topics for debugging and reprocessing.
- Outbox pattern - Guarantee message publication only when database transactions commit.
- TTL - Automatically expire stale messages to prevent backlogs and reduce noise.
High-level Messaging Abstraction
Use one consistent API across all brokers and programming languages without learning each broker’s client library or operational model. Swap brokers or evolve infrastructure without modifying application code.
- One API for all brokers - Kafka, RabbitMQ, Redis Streams, Azure Service Bus, AWS SNS/SQS, Google Pub/Sub, and more.
- HTTP + SDK access - Publish and subscribe using a HTTP only, or a single SDK, no broker-specific messaging expertise required.
- Infrastructure-neutral messaging layer - Decouple application logic from broker configuration and operational details.
- CloudEvents - Standardize event structure across systems with a vendor-neutral format.
Getting Started
Get started with the Catalyst Pub/Sub API quickstart. Then dive into more Pub/Sub quickstarts and deep dive into the documentation.