Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.

README.md 4.4 KiB

7 anos atrás
7 anos atrás
7 anos atrás
7 anos atrás
7 anos atrás
8 anos atrás
8 anos atrás
8 anos atrás
8 anos atrás
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174
  1. <p align="right">
  2.   <a href="https://github.com/dotnetcore/CAP/blob/master/README.zh-cn.md">中文</a>
  3. </p>
  4. # CAP
  5. [![Travis branch](https://img.shields.io/travis/dotnetcore/CAP/master.svg?label=travis-ci)](https://travis-ci.org/dotnetcore/CAP)
  6. [![AppVeyor](https://ci.appveyor.com/api/projects/status/4mpe0tbu7n126vyw?svg=true)](https://ci.appveyor.com/project/yuleyule66/cap)
  7. [![NuGet](https://img.shields.io/nuget/vpre/DotNetCore.CAP.svg)](https://www.nuget.org/packages/DotNetCore.CAP/)
  8. [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/dotnetcore/CAP/master/LICENSE.txt)
  9. CAP is a .Net Standard library to achieve eventually consistent in distributed architectures system like SOA,MicroService. It is lightweight,easy to use and efficiently.
  10. ## OverView
  11. CAP is a library that used in an ASP.NET Core project, Of Course you can ues it in ASP.NET Core with .NET Framework.
  12. You can think of CAP as an EventBus because it has all the features of EventBus, and CAP provides a easier way to handle the publishing and subscribing than EventBus.
  13. CAP has the function of Message Presistence, and it makes messages reliability when your service is restarted or down. CAP provides a Publish Service based on Microsoft DI that integrates seamlessly with your business services and supports strong consistency transactions.
  14. This is a diagram of the CAP working in the ASP.NET Core MicroService architecture:
  15. ![](http://images2015.cnblogs.com/blog/250417/201707/250417-20170705175827128-1203291469.png)
  16. > The solid line in the figure represents the user code, and the dotted line represents the internal implementation of the CAP.
  17. ## Getting Started
  18. ### NuGet (Coming soon)
  19. You can run the following command to install the CAP in your project.
  20. If your Message Queue is using Kafka, you can:
  21. ```
  22. PM> Install-Package DotNetCore.CAP.Kafka -Pre
  23. ```
  24. or RabbitMQ:
  25. ```
  26. PM> Install-Package DotNetCore.CAP.RabbitMQ -Pre
  27. ```
  28. CAP provides EntityFramework as default database store extension :
  29. ```
  30. PM> Install-Package DotNetCore.CAP.EntityFrameworkCore -Pre
  31. ```
  32. ### Configuration
  33. First,You need to config CAP in your Startup.cs:
  34. ```cs
  35. public void ConfigureServices(IServiceCollection services)
  36. {
  37. ......
  38. services.AddDbContext<AppDbContext>();
  39. services.AddCap()
  40. .AddEntityFrameworkStores<AppDbContext>()
  41. .AddKafka(x => x.Servers = "localhost:9092");
  42. }
  43. public void Configure(IApplicationBuilder app)
  44. {
  45. .....
  46. app.UseCap();
  47. }
  48. ```
  49. ### Publish
  50. Inject `ICapPublisher` in your Controller, then use the `ICapPublisher` to send message
  51. ```cs
  52. public class PublishController : Controller
  53. {
  54. private readonly ICapPublisher _publisher;
  55. public PublishController(ICapPublisher publisher)
  56. {
  57. _publisher = publisher;
  58. }
  59. [Route("~/checkAccount")]
  60. public async Task<IActionResult> PublishMessage()
  61. {
  62. //Specifies the message header and content to be sent
  63. await _publisher.PublishAsync("xxx.services.account.check", new Person { Name = "Foo", Age = 11 });
  64. return Ok();
  65. }
  66. }
  67. ```
  68. ### Subscribe
  69. **Action Method**
  70. Add the Attribute `[CapSubscribe()]` on Action to subscribe message:
  71. ```cs
  72. public class PublishController : Controller
  73. {
  74. private readonly ICapPublisher _publisher;
  75. public PublishController(ICapPublisher publisher)
  76. {
  77. _publisher = publisher;
  78. }
  79. [NoAction]
  80. [CapSubscribe("xxx.services.account.check")]
  81. public async Task CheckReceivedMessage(Person person)
  82. {
  83. Console.WriteLine(person.Name);
  84. Console.WriteLine(person.Age);
  85. return Task.CompletedTask;
  86. }
  87. }
  88. ```
  89. **Service Method**
  90. If your subscribe method is not in the Controller,then your subscribe class need to Inheritance `ICapSubscribe`:
  91. ```cs
  92. namespace xxx.Service
  93. {
  94. public interface ISubscriberService
  95. {
  96. public void CheckReceivedMessage(Person person);
  97. }
  98. public class SubscriberService: ISubscriberService, ICapSubscribe
  99. {
  100. [CapSubscribe("xxx.services.account.check")]
  101. public void CheckReceivedMessage(Person person)
  102. {
  103. }
  104. }
  105. }
  106. ```
  107. Then inject your `ISubscriberService` class in Startup.cs
  108. ```cs
  109. public void ConfigureServices(IServiceCollection services)
  110. {
  111. services.AddTransient<ISubscriberService,SubscriberService>();
  112. }
  113. ```
  114. ## Contribute
  115. 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.
  116. ### License
  117. [MIT](https://github.com/dotnetcore/CAP/blob/master/LICENSE.txt)