4 ms·
As an ex-fang engineer myself, I have never advocated for more services, usually have pushed for unifying repos and multiple build targets on the same codebase.
by mattnewton 2y ago
As an ex-fang engineer myself, I have never advocated for more services, usually have pushed for unifying repos and multiple build targets on the same codebase. I am forever chasing the zen of google3 the way I remember it.
If anything my sin has been forgetting how much engineering went into supporting the monorepo at Google and duo-repo at Facebook when advocating for it.
- paperplatter 2y agoDo FAANG engineers normally advocate for more services instead of fewer? I haven't gotten that impression.
- aleksiy123 2y agoSmaller services but not necessarily more binaries. The current direction I think is to build composable services that could be run together or separately. Where a service is a logical grouping of an RPC interface. Here is some public work in this direction from Google https://serviceweaver.dev/ https://serviceweaver.dev/
- paperplatter 2y agoMakes sense, since Google uses a monorepo (google3).
- paulddraper 2y agoNormally more services and fewer repos. From my experience.
- recursivecaveat 2y agoWhat were the two facebook repos? I can't find any reference to them.
- simscitizen 2y agoThe main ones were www which contained most of the PHP code and fbcode which contained most of the other backend services. There were actually separate repos for the mobile apps also.
- disgruntledphd2 2y agoFbcode then became fbsource when it acquired the android and some data code.
- ecshafer 2y agoThere seems to be more interest in building monorepo support now. Some tools, start ups, etc. I would bet Github is working on increasing support as well for large repos. So I think Google was ahead of the curve there.