As we go deeper into our microservices development, we see various pitfalls ahead. Now that our microservices are ready and when we think of clients utilizing those microservices, we will encounter the following issues:
- The consumer or the web client runs on a browser. We don't have any discovery client on the frontend, which takes care of identifying where the container/VM service is located or neither take care of load balancing. We need an extra piece of the puzzle which connects the microservices living in different containers in the backend and abstracting that implementation from the client.
- Untill now, we haven't spoken about centralized concerns like authenticating services, versioning services, filtering or transforming any request/response. Upon reflection, we realize that they need a central point of control from which they can be applied throughout the system without re-implementing the same logic everywhere.
- Further more, different clients may have different...