Edition 0 Updated to asp. Net core 0

The CAP Theorem
https://en.wikipedia.org/wiki/CAP_theorem
 
•
What is CAP Theorem?
https://www.quora.com/What-Is-CAP-Theorem-1
 
•
Data Consistency Primer
https://learn.microsoft.com/previous-versions/msp-n-p/dn589800(v=pandp.10)
 
•
Rick Salin
g. The CAP Theorem: Why “Everything is Different” with the Cloud and Internet
https://learn.microsoft.com/archive/blogs/rickatmicrosoft/the-cap-theorem-why-everything-is-
different-with-the-cloud-and-internet/
 
•
Eric Brewer. CAP Twelve Years Later: How the “Rules” Have Changed
https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed
 
•
CAP, PACELC, and Microservices
https://ardalis.com/cap-pacelc-and-microservices/
 
•
Azure Service Bus. Brokered Messaging: Duplicate Detection
https://github.com/microsoftarchive/msdn-code-gallery-
microsoft/tree/master/Windows%20Azure%20Product%20Team/Brokered%20Messaging%20Du
plicate%20Detection
 
•
Reliability Guide
(RabbitMQ documentation) 
https://www.rabbitmq.com/reliability.html#consumer
 
Testing ASP.NET Core services and web apps 
Controllers are a central part of any ASP.NET Core API service and ASP.NET MVC Web application. As 
such, you should have confidence they behave as intended for your application. Automated tests can 
provide you with this confidence and can detect errors before they reach production. 
You need to test how the controller behaves based on valid or invalid inputs, and test controller 
responses based on the result of the business operation it performs. However, you should have these 
types of tests for your microservices: 
•
Unit tests. These tests ensure that individual components of the application work as expected. 
Assertions test the component API. 
•
Integration tests. These tests ensure that component interactions work as expected against 
external artifacts like databases. Assertions can test component API, UI, or the side effects of 
actions like database I/O, logging, etc. 

---

153 
CHAPTER 5 | Designing and Developing Multi-Container and Microservice-Based .NET Applications 
•
Functional tests for each microservice. These tests ensure that the application works as expected 
from the user’s perspective.
•
Service tests. These tests ensure that end-to-end service use cases, including testing multiple 
services at the same time, are tested. For this type of testing, you need to prepare the 
environment first. In this case, it means starting the services (for example, by using docker-
compose up).