3 ms·
> With something like a Java interface, it doesn't really matter if those APIs change because all the code is built and released together at HEAD. Right, this
by roughly 5y ago
> With something like a Java interface, it doesn't really matter if those APIs change because all the code is built and released together at HEAD.
Right, this is the thing that winds up following from the monorepo - the monorepo problem goes away if we just release everything, the whole fuckin’ system, into production every time we make any update to master. If that’s your system, hats off to you, I’m not nearly that good of an engineer.
- barrkel 5y agoIt's actually easier, in many ways -- if you can manage to release continuously. It forces you to stage your code incrementally and you should be able to roll back things easily if you see breakage.
- deleted 5y ago[deleted]
- throwaways885 5y agoIf your services are backwards compatible to talk to each other, then you don't need to release instantly. Making breaking changes is tricky, but you don't need to release everything.