>> I'm pretty staunchly in the "one service, for one deployment artifact, for one CI pipeline, for one repo" camp
This seems reasonable if nothing is shared. If there are any shared libraries then you are back to binary sharing (package managers, etc.) with this approach.
Mono-repo and monolith are orthogonal concepts.
>> I'm pretty staunchly in the "one service, for one deployment artifact, for one CI pipeline, for one repo" camp
This seems reasonable if nothing is shared. If there are any shared libraries then you are back to binary sharing (package managers, etc.) with this approach.