4 ms·
If you make backwards-incompatibilities API changes like this, you also need simultaneous/atomic deploys across all services. On the other hand, if you aren’t
by konschubert 7y ago
If you make backwards-incompatibilities API changes like this, you also need simultaneous/atomic deploys across all services.
On the other hand, if you aren’t doing simultaneous/atomic deploys, then having a monorepo may actually be an obstruction.
- opportune 7y agoYeah, that's the part I left out because it does get complicated when it comes to releases. For simplicity's sake, let's say everything actually gets bundled into one binary and released together.
- yjftsjthsd-h 7y ago> bundled into one binary and released together. In fairness, that's the canonical test for "should this be 1 repo"
- lrem 7y agoNot always. Renaming a proto field is one common example.