4 ms·
Yep. Have also seen this coupled with the microservices pattern of having all the microservices share a large common library, with all microservices built toge
by Scubabear68 4y ago
Yep.
Have also seen this coupled with the microservices pattern of having all the microservices share a large common library, with all microservices built together and deployed together all the time. All the pain of shared code across teams plus the pain of shared DB plus the pain of debugging across completely arbitrary process boundaries.
- karmakaze 4y agoSounds like a cargo-culted monorepo.
- layer8 4y agoThis can actually make sense when you have loosely coupled services that mostly talk to the database and external systems, and not directly to each other, that have a common domain model (due to the shared database) and common helper libraries, and that you want to be restartable separately, and/or be distributed over several hosts. Of course, the process boundaries should be well-chosen and not arbitrary.