>Adding a network boundary in production just to serve some code organization purpose during development seems completely unnecessary to me. That's a pretty co

>Adding a network boundary in production just to serve some code organization purpose during development seems completely unnecessary to me. That's a pretty common approach. Service oriented architecture isn't necessarily "development" purposes, usually more generic "business" purposes but organization layout and development team structure are factors. From an operational standpoint, it's valuable to limit the scope and potential impact code deploys have--strong boundaries like the network offers can help there. In that regard, you're serving a "development" purpose of lowering the risk of shipping new features.