News for hackers. Stuff that matters.
Re:Goodbye Microservices: From 100s of problem children to 1... by jdoliner on Tuesday July 10, 2018 @11:18PM (#17504222)
> This is horrible at scale.

This can work fine at scale, Google does it with however many tens of thousands of engineers they have these days. Having everything in a monorepo doesn't solve the communication problem, it doesn't prevent solving it either.

Re:Goodbye Microservices: From 100s of problem children to 1... by eitally on Wednesday July 11, 2018 @12:59AM (#17504553)
Sort of. Google is also well known for having a dozen chat apps. What most people don't know is that there are also likely a dozen different libraries/utilities/interfaces performing near identical services just because an engineer or product team weren't 100% satisfied with what already existed. So yes, it's a monorep, but holy heck there's a lot of duplicative cruft.
Re:Goodbye Microservices: From 100s of problem children to 1... by seabrookmx on Wednesday July 11, 2018 @02:37AM (#17504883)
> all code deployed to all servers This is the main point of the post. Google most certainly doesn't do this, even if they have all their code (or at least, all their private code) in one repo (piper).