Fine-grained architecture divides application functionality among many small services or components. This can make seemingly simple changes span multiple services, increasing design complexity, operational coordination, and the number of interactions that must remain correct. section 2.2.4
The main forces and consequences are:
- Cross-service requests can require complex Saga workflows to preserve data consistency. section 2.2.4
- Long chains of REST calls create tight runtime coupling, allowing one unavailable service to fail the whole request. section 2.2.4
- Frequent network trips and large inter-service transfers can produce high latency and poor performance. section 2.2.4
- Prefer incremental migration from a monolith when microservices provide a tangible benefit; avoid adopting a microservices-first design without a demonstrated need. section 2.3
FTGO order processing
An order request could cross enough services that a courier was not assigned, or a prompt cancellation failed to refund the customer. These failures were difficult to diagnose because complex service interactions obscured the underlying data-consistency bugs. section 2.2.4
