3 ms·
I find this highly misleading, Facebook is famously a big monolith, and I think so is instagram. There’s plenty of services and a couple micro services as well,
by phyrex 3y ago
I find this highly misleading, Facebook is famously a big monolith, and I think so is instagram. There’s plenty of services and a couple micro services as well, but I don’t think anybody would characterize meta as having a micro services architecture. I have no idea what the authors’ agendas are, but something isn’t right there.
- MarkSweep 3y agoThe article mentions that www, the monolithic PHP code base, is 4.6% of the service instances. Though the paper does not mention the compute allocation. I do not recall how www is deployed, but it’s easy to imagine it’s allocated a lot more resources than a lot of other services are.
- phyrex 3y ago> At Meta, 0.1% and 1% of the largest services consume 40% and 80% of the total fleet capacity, respectively. from https://www.usenix.org/system/files/osdi23-grubic.pdf https://www.usenix.org/system/files/osdi23-grubic.pdf
- yuliyp 3y agoLarge, unsharded services are generally going to run one instance per machine alone as that's the most efficient way to run most of them (reduce per-instance overhead as much as possible). Small (true "micro") services or other things which have instances per use case (like the inference platform example given in the paper) may use a small fraction of a machine.
- yuliyp 3y agoThere is a Hack monolith (the www tier). There are also a huge number of other services, ranging from micro with a couple instances globally to "larger than almost anyone elses's monolith".