liveBook · Manning

Chapter 2: FTGO: A case study in moving from one kind of development hell to another

What you will learn in chapter 2 of Microservices Patterns, Second Edition

The chapter introduces FTGO’s move from an outgrown monolith to microservices as a case where a suitable architectural choice still went badly wrong.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduces FTGO’s move from an outgrown monolith to microservices as a case where a suitable architectural choice still went badly wrong.

Key terms: FTGO, monolithic architecture, microservice architecture, fast flow success triangle

2.1 FTGO architecture V1: The eventual descent into monolithic hell

This section introduces how FTGO’s initially successful monolith became a large, poorly structured application that slowed development as the company grew.

Key terms: monolith, Java Web Application Archive (WAR) file, Big Ball of Mud

2.1.1 The architecture of the FTGO application

The section describes FTGO’s hexagonal application structure and explains why its logically modular design was initially deployed as a monolith.

Key terms: hexagonal architecture, business logic, modules, inbound adapters, outbound adapters, logically modular architecture, single WAR file, monolithic architecture

2.1.2 Why the monolithic architecture worked well initially

This section explains why FTGO’s monolithic architecture was initially convenient, while noting that its advantages eroded over time.

Key terms: monolithic architecture, radical changes, database schema, end-to-end tests, REST API, Selenium, WAR file, Tomcat, load balancer

2.1.3 Living in what they thought was monolithic hell

This section explains why FTGO’s growing monolith made development, deployment, reliability, scaling, and technology upgrades increasingly difficult.

Key terms: hexagonal architecture, domain, big ball of mud, edit-build-run-test loop, IDE, feature branches, Continuous Integration (CI) server, unreleasable state, testing cycle, testability

2.2 FTGO architecture V2: Fine-grained microservices everywhere - a different kind of hell

Introduces why FTGO decided to replace its monolith with microservices, setting up the account of its V2 architecture.

Key terms: monolithic hell, monolithic architecture, microservice architecture

2.2.1 How FTGO adopted the microservice architecture

This section describes FTGO’s two approaches to adopting microservices and notes how long its application rewrites took.

Key terms: microservice architecture, microservices-first approach, rewrites

2.2.2 The V2 architecture of the main FTGO application

This section describes FTGO’s V2 application as a collection of services whose boundaries, sizes, and data ownership varied across teams.

Key terms: business domains, technical capabilities, services, Order Service, Courier Service, Order Data Service, Courier Data Service, Order Management team, Consumer Management, Consumer Profile Service

2.2.3 What worked well with the V2 architecture

This section identifies the benefits FTGO gained from its V2 architecture while noting that the architecture also brought severe problems.

Key terms: simpler components, team autonomy, services, technology stacks, technology stack upgrades, segregate modules by characteristics

2.2.4 What went wrong with their microservice architecture

FTGO’s V2 case shows how fine-grained services, neglected deployment and coupling practices, and poorly chosen migration strategies undermined the benefits the company expected from microservices.

Key terms: independent deployability, QA team, end-to-end tests, manual testing, design-time coupling, data services, Order Data Service, MenuItem, OrderLineItem, API evolution

2.3 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 1: Microservices: an architecture for fast flow Chapter 3: Software architecture: what is it, why does it matter and who does it? →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.