> No mentions of microservices, serverless architecture, application boundaries, event-driven architecture, and the lot. I see why one would want to escape the

> No mentions of microservices, serverless architecture, application boundaries, event-driven architecture, and the lot. I see why one would want to escape the mindless name-dropping that can be prevalent elsewhere, but at the same time, things have a name/fame for a reason. There is pragmatic value in studying patterns (especially from good sources), and citing them in your internal documents so everyone is on the same page.