A microservices-first approach starts new applications—or rewrites existing ones—as microservices instead of first considering a monolith. It is attractive when teams expect independent deployment and rapid delivery, but those benefits depend on loose design-time coupling, suitable service boundaries, and supporting delivery practices. section 2.2.1 section 2.3
Use the approach cautiously:
- Prefer incremental migration when an existing monolith has a tangible problem that microservices can solve; it provides continual feedback on service design. section 2.3
- Avoid treating every application as a collection of fine-grained services. Without independent deployability and loose coupling, the result can combine tight design-time and runtime coupling with poor performance. section 2.2.4 section 2.3
- Pair microservices with DevOps and Team Topologies practices; otherwise handoffs, broad end-to-end testing, and manual testing can keep deployments slow and outages difficult to diagnose. section 2.2.4 section 2.3
FTGO adoption
FTGO rewrote its main application and acquired applications as microservices, while also applying the approach to new applications. The main application’s V2 architecture eventually worked, but delivered infrequent, large deployments; tight coupling, inconsistent data, poor performance, and difficult technology upgrades showed that adopting microservices alone was insufficient. section 2.2.1 section 2.2.4

