Skip to content
CAI
Produce a survey ↗Verify a survey

dotnetcore/CAP

CAP is a distributed transaction and messaging framework for .NET that provides reliable, eventual consistency across microservices. It supports a wide variety of message brokers (such as Kafka, RabbitMQ, and Azure Service Bus) and persistence backends (including SQL Server, PostgreSQL, and MongoDB) to ensure message delivery and state management. The system also includes a comprehensive monitoring dashboard for observing message flow and subscriber status.

58.0

Adequate · 29 July 2026

20k

lines of production code

C#

primary language

1

bus factor · 145 authors in all

3

measurements over time

CAI band scale
CAI trend line

How it got here

2016–2017 · CAP rebranding and architecture modernization

The project underwent a major rebranding from 'kafkabus' to 'CAP', accompanied by a comprehensive documentation overhaul. The codebase was significantly refactored to support .NET 10, with new modular processor architectures, improved connection pooling, and expanded storage/transport options including PostgreSQL, MySQL, and SQL Server integrations.

20 changes

2018–2019 · Storage and transport abstraction

This period focused on abstracting the CAP library's architecture by introducing new interfaces for persistence, serialization, and transport layers. It added support for multiple storage backends, including MongoDB, in-memory, and SQL Server, while also enhancing message broker integrations for Azure Service Bus and Kafka.

19 changes

2020–2022 · multi-broker and dashboard modernization

This period focused on expanding CAP's transport layer by adding support for NATS, Amazon SQS, and Apache Pulsar, alongside a complete frontend migration of the dashboard to Vue.js. The work also introduced a new subscriber filter pipeline for async processing and added OpenTelemetry instrumentation for distributed tracing.

16 changes

2023–2024 · Azure Service Bus and Dashboard enhancements

This period focused on expanding Azure Service Bus support with session and custom topic configuration, alongside a critical fix for broker address resolution. Concurrently, the project introduced Kubernetes service discovery for the CAP Dashboard and added a JWT-secured sample application.

5 changes

CAI lens gauges

Survey your own repository

dotnetcore/CAP was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.

Survey a repository

About this page

  • The description of this project is derived from its own commit history, not from its README.
  • The score is its highest published measurement, taken on 29 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit e52b8508e5 — the exact code this score is about.
  • Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.
CAI link cards