Companies that aren’t B2D have a hard time with monolithic architecture. They simply have too many disparate needs, teams, vendors, and timelines to try to forc

Companies that aren’t B2D have a hard time with monolithic architecture. They simply have too many disparate needs, teams, vendors, and timelines to try to force everyone to share a codebase, unit of deployment, and set of endpoints. The supply side and demand side of any business has vastly different objectives, SLAs and priorities. Should we have to wait two weeks to deploy a minor patch to the Purchase Order portal because there is a risky ecommerce deployment that needs to be finalized first? Do we need to scale up the web servers to batch process some nightly data? Surely there are excesses in the realm of microservice architecture… “every library is a microservice…” is advice I’ve read in the past. Service discovery / routing isn’t easy. Naming things is hard. Personally I prefer the term Service and try to make no prescriptions as to what size it will end up being.