So far, we used two patterns in our news portal and nothing is preventing us from applying more patterns as needed. However, in some cases, it may not be necessary to apply more than one pattern, and the proxy design pattern is sufficient for the application context.
With the scenario described earlier, the most desirable approach is to keep, or try to keep, as many pure microservices as possible, which means microservices that are sufficient in themselves. When microservices need to communicate using a synchronous protocol with another microservice, primarily in the Internal Service layer, we say that this is not pure.
The non-purism of microservices can generate scalability issues and even availability issues because of overhead ...
