dotnetcore/CAP
CAP
CAP is a .NET distributed transaction framework and event bus designed to manage asynchronous communication in microservices. It implements the outbox pattern to ensure eventual consistency and reliable message delivery by persisting messages in local database tables until transactions commit.
The framework includes a distributed message monitor and web dashboard for tracking the status of sent and received messages. It provides tools for event traffic visualization, distributed request tracing, and the ability to manually trigger retries for failed delivery attempts.
The system supports various messaging patterns, including topic-based routing, delayed message processing, and competing consumer models for load balancing. Reliability is managed through automatic retry mechanisms, backpressure flow control to prevent memory exhaustion, and configurable processing modes for either parallel throughput or sequential execution.
Features
- Event Bus Architectures - Provides a core event bus architecture for asynchronous message passing and decoupled service communication.
- Atomic Event Publishing - Ensures that database state changes and corresponding event notifications are committed as a single atomic unit using the outbox pattern.
- Messaging Reliability - Ensures messaging reliability between decoupled services through guaranteed delivery and automatic retry mechanisms.
- Eventual Consistency Orchestrators - Maintains data integrity across separate services through guaranteed message delivery and automated retries.
- Message Delivery Guarantees - Guarantees message delivery by automatically retrying failed attempts until the destination acknowledges receipt.
- At-Least-Once Delivery Guarantees - Ensures at-least-once delivery guarantees through a polling mechanism and automatic retries of failed messages.
- Distributed Transaction Management - Manages data integrity across multiple microservices using eventually consistent transactions and the outbox pattern.
- Event-Driven Architectures - Provides a framework for building reactive, event-driven architectures that respond to state changes via asynchronous events.
- Event Driven Messaging - Provides a lightweight event bus for coordinating services through asynchronous message delivery and pub-sub patterns.
- .NET Distributed Transaction Frameworks - Provides a comprehensive .NET framework for managing distributed transactions in microservices using eventual consistency.
- Transactional Outbox Patterns - Implements the transactional outbox pattern by persisting messages in local database tables to ensure eventual consistency.
- Delayed Message Queuing - Allows sending messages to a queue with a defined waiting period before they become available for processing.
- Message Routing - Implements targeted message routing using attribute-based, wildcard, or partial topic subscriptions to distribute messages to specific consumers.
- Message Order Enforcement - Enforces strict execution order for messages to maintain data consistency across distributed service operations.
- Event Flow Visualizers - Includes a web dashboard for real-time visualization of event traffic and the flow of messages across nodes.
- Message Status Dashboards - Ships a web dashboard for tracking the status of sent and received messages across distributed nodes.
- Microservices Communications - Orchestrates communication workflows between microservices using event topics and subscription groups.
- Event Subscription Bindings - Provides the ability to bind service methods to event topics, triggering logic when matching messages arrive.
- Consumer Group Coordinators - Provides consumer group coordination to distribute message processing across multiple service instances for load balancing.
- Topic Routing Patterns - Implements advanced topic routing patterns using wildcards and attribute matching to deliver messages to specific consumers.
- Flow Control Mechanisms - Implements flow control mechanisms to regulate message throughput and prevent memory exhaustion during data spikes.
- Distributed Tracing Systems - Provides distributed request tracing to monitor the flow of messages across multiple microservice nodes.
- Message Delivery Management - Offers a web dashboard for viewing message status and manually triggering retries for failed delivery attempts.
- Message Queues - Event bus with local persistence for RabbitMQ or Kafka.
- Application Frameworks - EventBus for microservice integration and SOA.
