One of the key challenges in microservice development is fixing the scope of a microservice:
- If a microservice is too big, you end up in monolithic hell and get stuck in a huge turnaround time, with difficulty adding new features and implementing bug fixes
- If a microservice is too small, either we end up with tight coupling among services or too much code duplication and resource consumption
- If a microservice size is right, but the bounded context isn't fixed, such as services sharing a database, it leads to higher coupling and dependencies
In this section, we are going to devise an implementation plan for our shopping cart microservices. We will formulate a general workflow or plan and ...