11–20 of 182 posts
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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?
I don't know that it's a bad effort, but it's one that rose and died seemingly the same day.
I feel like more time with a good product person would have given more thought to fit, advertising, release, and so on.
Very 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?
Their infrastructure is cloudy, but it's built around mostly a single customer and assumes the infrastructure software people and the application software people communicate deeply and continously. Running on a public cloud isn't that similar, at least as a small customer.
Could they pivot towards being a cloud service? Probably, but they'd need to do a lot of work to make their platform viable and to earn trust of potential customers, and they'd be entering a crowded market; there's already 6 S&P100 companies in Cloud (Amazon, Google, Microsoft, Oracle, IBM, Salesforce), and tons of smaller players.
IMHO, given their revenues and profit margins, there's no reason to do all the work it would take to offer cloud services too. Unless there's some opportunistic large customer deal made. They also might also need to renegotiate their content node agreements if they use them to serve cloud customer traffic, and that's a long process.
This approach appears to be one of the most optimal designs for software networking (service mesh) and for storage (database operations) for organizations with large server counts. I was surprised to see their IP networking to follow the same model, rather than primarily relying on BGP.
It was omitted in this paper, but I would expect for local caching to be used to reduce load on L7 routers and for improved latency for database queries. Clients can invalidate caches and perform another lookup to the service mesh after a reasonable timeout (100-500ms).
> 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.
Is there any public information available for the deploy/observability tool?
Not a word about Thrift, perhaps it was too low level for an infra overview, but I would have expected it to make some technical impact from a global perspective.
Earlier quoted context omitted.
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? It has more than 300M users.
I'm talking specifically about its launch.
Earlier quoted context omitted.
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? It has more than 300M users.