3.0 KiB
Title: CAP - A distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
CAP
[](https://travis-ci.org/dotnetcore/CAP)
[](https://ci.appveyor.com/project/yuleyule66/cap/branch/master)
[](https://www.nuget.org/packages/DotNetCore.CAP/)
[](https://www.nuget.org/packages/DotNetCore.CAP/)
[](https://raw.githubusercontent.com/dotnetcore/CAP/master/LICENSE.txt)
[](https://github.com/dotnetcore)
CAP is a library based on .net standard, which is a solution to deal with distributed transactions, also has the function of EventBus, it is lightweight, easy to use, and efficiently.
Introduction
In the process of building an SOA or MicroService system, we usually need to use the event to integrate each services. In the process, the simple use of message queue does not guarantee the reliability. CAP is adopted the local message table program integrated with the current database to solve the exception may occur in the process of the distributed system calling each other. It can ensure that the event messages are not lost in any case.
You can also use the CAP as an EventBus. The CAP provides a simpler way to implement event publishing and subscriptions. You do not need to inherit or implement any interface during the process of subscription and sending.
!!! Tip “CAP implements the Outbox Pattern described in the eShop ebook”
> Atomicity when publishing events to the event bus with a worker microservice
For detailed instructions see the Getting Started Guide.
Contributing
One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
If you have any question or problems, please report them on the CAP repository:
License
CAP is licensed under the MIT license.