Proxy strategy to orchestrator

The proxy design pattern does not have an elaborated strategy for data orchestration. As already discussed earlier in this chapter, the proxy performs tasks only at the request level. Of course, some information from a request may receive special treatment, but it does not compare to what we saw in the orchestrator design pattern.

When we talk about data orchestration using the proxy design pattern, we are looking directly at the request. The approach using proxy does not preclude the adoption of another pattern for microservices; sometimes, it is of great help to migrate monolithic to microservices.

Imagine that we have a monolithic application that we want to decompose and move its domains to microservices. The initiative is commendable, but we cannot stop developing new features while we are shutting down the monolithic application. Soon, the strategy will be to use the proxy design pattern to keep the application working, while we move the business and apply...