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: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1
💥 Join this channel to get access to source code & demos!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join
🔥 Don't have the JOIN button? Support me on Patreon!
https://www.patreon.com/codeopinion
📝 Blog: https://codeopinion.com
👋 Twitter: https://twitter.com/codeopinion
✨ LinkedIn: https://www.linkedin.com/in/dcomartin/
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion
0:00 Intro
0:33 Physical Boundaries
2:43 4+1 Architectural View Model
3:39 Logical Boundaries
5:47 Complexity
#softwarearchitecture #softwaredesign #microservices
