4 ms·
Keeping the spirit of microservices alive is super duper important, so not entwining two services with shared code or responsibilities is key, and forcing inter
by SpeedilyDamage 4y ago
Keeping the spirit of microservices alive is super duper important, so not entwining two services with shared code or responsibilities is key, and forcing interaction to happen through their defined APIs.
- lliamander 4y agoYeah, that's pretty much what I do as well. Shared libraries get their own repo as well and are published in a package manager. Honestly, in terms of enabling concurrent development across multiple teams while simply using common OSS software, polyrepo seems a lot easier.