2 ms·
Architect here: I work in Azure; I love Azure; I totes feel your pain about Azure. Half of my solutions are hopscotching networks and NICs between services that
by ajcp 3y ago
Architect here: I work in Azure; I love Azure; I totes feel your pain about Azure. Half of my solutions are hopscotching networks and NICs between services that should all just be one service. There are no obvious or repeatable patterns or configurations; every answer is "the right answer", which as an architect drives me up the f*king wall.
I know MSFT likes to sell that as "complete and flexible configuration" but more often than not it's like: if your prescription to use this one service is so rigid as to use these four other services in such a way then when not just package them completely as such?