The proxy design pattern is relatively simple to maintain and understand when compared to other patterns, whether they are architectural patterns or not. Although it is a simple pattern, there are some points requiring attention, which may not be well-observed, implying possible critical points of failure.
It's always good to emphasize that seeing errors in microservices, primarily under an architectural vision, is not something simple. There are some points that deserve greater emphasis on good practice.
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...