Meta’s Hyperscale Infrastructure: Overview and Insights
1–10 of 182 posts
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#2I find it interesting how they describe the PHP web front end as a "serverless" or "function as a service" architecture. I guess it's a matter of perspective. It's a service that has a monolithic codebase with lots of endpoints deployed to it. I guess from the perspective of the maintainer of one of those endpoints it's "serverless" but that abstraction (like all abstractions) has leaks: the teams responsible for the top endpoints and those working on shared libraries can't treat the infra as a given, but rather need to be acutely aware of its limitations and performance characteristics.
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#3Very interesting, in particular the explicit comparisons with hyperscalers.
I almost wonder if this is preparation for them launching their own public cloud. Anyone from Meta care to comment?
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#4> Moreover, once it [Threads] was developed, the infrastructure teams were given only two day’s notice to prepare for its production launch. Most large organizations would take longer than two days just to draft a project plan involving dozens of interdependent teams, let alone execute it. At Meta, however, we quickly established war rooms across distributed sites, bringing together both infrastructure and product teams to address issues in real-time. Despite the tight timeline, the app’s launch was highly successful, reaching 100 million users within just five days, making it the fastest-growing app in history.
Kind of more impressive to have kept this ability to ship fast than anything else. A lot of work is needed to not let the bureaucracy increase and stop the lawyers or other functions from creating approval gates everywhere. Or at least to be able to have war rooms that can get it done so quickly.
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#5> Moreover, once it [Threads] was developed, the infrastructure teams were given only two day’s notice to prepare for its production launch. Most large organizations would take longer than two days just to draft a project plan involving dozens of interdependent teams, let alone execute it. At Meta, however, we quickly established war rooms across distributed sites, bringing together both infrastructure and product te…
[deleted]
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#6Very interesting, in particular the explicit comparisons with hyperscalers. I almost wonder if this is preparation for them launching their own public cloud. Anyone from Meta care to comment?
It would be pretty impressive to launch a public cloud I would trust even less than GCP :D
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#7> Moreover, once it [Threads] was developed, the infrastructure teams were given only two day’s notice to prepare for its production launch. Most large organizations would take longer than two days just to draft a project plan involving dozens of interdependent teams, let alone execute it. At Meta, however, we quickly established war rooms across distributed sites, bringing together both infrastructure and product te…
I thought the same thing, but then realize that Threads was a huge flop.
Is it really a skill to very quickly release a dud app?
I don't know the answer to that. Bypassing bureaucracy seems like heaven, but it feels like it also bypassed the product folks entirely.
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#8Is there any public information available for the deploy/observability tool?
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#9> Moreover, once it [Threads] was developed, the infrastructure teams were given only two day’s notice to prepare for its production launch. Most large organizations would take longer than two days just to draft a project plan involving dozens of interdependent teams, let alone execute it. At Meta, however, we quickly established war rooms across distributed sites, bringing together both infrastructure and product te…
I thought the same thing, but then realize that Threads was a huge flop. Is it really a skill to very quickly release a dud app? I don't know the answer to that. Bypassing bureaucracy seems like heaven, but it feels like it also bypassed the product folks entirely.
What is threads lacking from a product perspective?
Re: Meta’s Hyperscale Infrastructure: Overview and Insights
#10Very interesting, in particular the explicit comparisons with hyperscalers. I almost wonder if this is preparation for them launching their own public cloud. Anyone from Meta care to comment?
It would be pretty impressive to launch a public cloud I would trust even less than GCP :D
GCP got this reputation because it’s a second class citizen within Google. Google’s own internal infra (Borg, Blaze) is top-notch.
If Meta can pull off the public cloud correctly, I’d trust them greatly - they’ve shown significant engineering and product competence till now, even if they could use some more consistent and stable UI.