We will use an online store as an example. We have seen that dividing the application by criticality, always respecting the boundaries of DDD, is very positive with respect to availability. We also saw that having the software to depend on is a really physical component that represents a big risk point. However, much of this may protect us from glitches or risks in the system architecture. There are times that it does not depend on our part. Sometimes, the external service will use microservices in our ecosystem.
In the case of the payment process in an online store, the microservice is the final step of the purchase, being responsible for completing the payment of the product requested by the client. Payment must be communicated using ...
