Microservices Are Not an Architecture. They Are a Consequence.

D
Dick Edidiong Bassey
·

The microservices cult has convinced many teams to start with microservices before understanding why services get decomposed from monoliths.

Microservices are a consequence of a successful monolith that has grown beyond the ability of a single codebase to change safely: deployment risk becomes unacceptable, teams need independent release cycles, or components have radically different scaling characteristics.

The SellTrove platform started as a Laravel monolith. The ML pricing, payment processing, and storefront services were extracted as they developed different scaling characteristics and deployment cadences.

"Microservices are modern" is not a reason. Start with a modular monolith. Extract services when you have a specific, measurable reason to.

— Dick Bassey | DevDick | 2024