Microservices gets it WRONG defining Service Boundaries

Logical boundaries aren't physical boundaries. A service boundary can be a 1:1 mapping of logical and physical but they don't have to be. A logical boundary can have many physical boundaries and a physical boundary can be composed of many components from many logical boundaries. Do we have microservices to thank for the idea that the physical, development, and logical views of a system are the same? This introduces a pile of unneeded complexity related to deployment, versioning, and data duplication. 🔗 EventStoreDB https://eventsto.re/codeopinion 🔔 Subscribe:    / @codeopinion   💥 Join this channel to get access to source code & demos!    / @codeopinion   🔥 Don't have the JOIN button? Support me on Patreon!   / codeopinion   📝 Blog: https://codeopinion.com 👋 Twitter:   / codeopinion   ✨ LinkedIn:   / dcomartin   📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo... 0:00 Intro 0:33 Physical Boundaries 2:43 4+1 Architectural View Model 3:39 Logical Boundaries 5:47 Complexity #softwarearchitecture #softwaredesign #microservices