In a business sense, absolutely not. Sure they could build it technically, but they'd lose money.<p>The issue isn't expanding data centers -- that's "easy". The issue is all of the software tooling, all of the gigantically massive platforms and services they have to not only build, but <i>catch up to</i> AWS/Google/Azure, all of which are moving targets.<p>AWS launched in 2002. Google Cloud (GCE) basically started in 2012 and only recently has finally mostly caught up to become a fully-fledged viable competitor, which took an entire <i>decade</i>. Meta would be too late to the party.<p>Sure they could launch something much smaller like a Digital Ocean competitor -- not a fully-featured cloud, mostly just servers and storage. But why would they? The margins are low and there's no strategic reason to do so.
Not a chance. For a very simple reason: data center operations are reliant on trust between the parties hosting and the operators. If the party that operates the data center has indicated in no uncertain terms that they will be more than happy to violate trust at every junction then that party will have an uphill battle convincing potential customers that 'of course that does not apply to them'.<p>Keep in mind that a hosting partner has physical access to your precious hardware, something that you yourself probably don't even have. As such they are ideally placed to violate your trust six ways from Sunday and if they don't have a clean track record in that respect and you go into business with them anyway you only have yourself to blame.
I think we are more likely to see Apple enter this market than Meta. I just don't think the company has the leadership with the vision to do it. They are too focused on being central to <i>users</i> lives to sell ads, and seem to be betting the company on VR which anyone outside the bubble can see has no place as a central social device.<p>Apple on the other hand will be looking at the cloud market and be thinking how can they do it differently? Not just compete selling a commodity, be create a step change in the market. I could see them utilising their silicone expertises and some creative thinking to launch a cloud system unlike what is currently available.
Nope. Pick a large AAA always online gaming company and ask the same question and I think the answer is the same. Just because a company runs a ton of IT infrastructure doesn't mean they would automatically be capable of running VM's for others.<p>As an aside, I would not trust data security on any solution Meta comes up with, their business model and ethos is user data for sale.
No. I worked there, and saw the services available to developers. There's a dizzying array, and many of those services are quite excellent. However, they're <i>deeply</i> intertwined with each other and often quite idiosyncratic. That's going to be a hard sell in a market where people are already used to the Amazon or Google or Microsoft versions.<p>There's a lot of automation, but it's mostly for the team running the service itself. If you're a <i>user</i> of a service, you're likely to be quite reliant on knowing a member of that team to get new allocations or resolve problems. This is fine for developers within a single org, but building out the self-service and multitenancy necessary to make it palatable to outside users would be a <i>major</i> undertaking even if all the oxygen weren't being sucked out of the rest of the company by metaverse stuff.<p>Lastly, that capacity is <i>already being actively used</i> and they're barely keeping up with building out enough new capacity. Where are the resources going to come from to support outside users?<p>It just doesn't make sense for them to try, technically or logistically or culturally. The last thing they need is more distractions.
Ex-Facebooker Ex-Googler here. IMHO? Absolutely not. Infrastructure just isn't in FB's DNA.<p>I've never worked at Amazon but my understanding was that AWS was born from bezos deciding one day that the whole company would adopt a microservices architecture and the basic technology for that became AWS. This is quintessential eat your own dogfood. They were first to market and committed a lot to it so they became dominant.<p>Google (IMHO) only ever really entered the cloud space because they were afraid of AWS becoming so large that Google would cease to be a price-maker in the hardware space and would be a price-taker. I think I read at one point Google was purchasing 1 in 10 hard disks produced globally. That gives you a lot of power to set prices and secure supply if you're smart. Google didn't want to lose that position to Amazon so Cloud became a means of creating demand for more hardware.<p>Internally, Google services run on what can only be described as a data center OS (ie Borg). You set resource constraints like how much memory and how many CPUs your processes need and there's a scheduler that makes sure you only share resources on a server with other processes within total constraints. There's more to this like flex resource scheduling but it'll do for this example. IIRC Linux's cgroups, which form the basis of this, were contributed to Linux by Google.<p>Even so, my understand was that Google Cloud was relatively inefficient through all the networking and cloud VM/resource layers. This was years ago so may no longer be true and I have no idea how this compares to Amazon. But Google is prepared to get through that for other reasons. Still, Google doesn't use Cloud internally (unlike Amazon).<p>Facebook does some things very well, particularly produce deployment. You really can push a diff to master and it just gets auto-deployed to prod 1-4 hours later. What's more you have a bunch of UI frameworks such that developing a fully-functional UI that fits the FB style is amazingly quick.<p>But on the infra side, everything I saw was a disaster. There were still different specs of servers and each server AFAIK only runs one thing. There's none of the resource constraining stuff Google has. So how would you deploy Cloud to such infra? The answer is you wouldn't because you'd have to rebuild it from scratch and/or create completely different infra to what the rest of the company uses.<p>FB's approach has always beeen to build things quickly and not worry about efficiency. That's not the recipe for success in a low-margin business like cloud.
They have no good reason to because AFAIK Microsoft and Google are still bleeding money with their cloud divisions because they have to hand out huge free credit grants to gain new customers.<p><a href="https://www.theinformation.com/articles/why-openai-spent-barely-a-dime-on-microsofts-cloud-after-1-billion-deal" rel="nofollow">https://www.theinformation.com/articles/why-openai-spent-bar...</a><p>"When Microsoft in 2019 said it had invested $1 billion in OpenAI, the high-profile artificial intelligence startup agreed to develop its products exclusively using Microsoft’s Azure cloud servers."
The move fast and break things aspect might be a knock against them.<p>But since Facebook has been trying to diversify I too am curious why they haven't tried their own cloud products yet.
There is a huge difference between running infrastructure on behalf of a single, well-intentioned business and running infrastructure that needs to deal with high density, adversarial multi-tenancy.<p>Not saying they can’t do it if they really committed, but the premise of the question that “they already have technical expertise” is flawed.<p>Btw, this is the similar learning curve that Google went through (and arguably still going through) when they decided that they could expose their awesome infra to external customers.
No, they would be almost 2 decades behind on building the required services and capturing market share. While they could make up the time on the tech side eventually, the market share is a very hard grind that they would not be able to pull off. Google has been trying and failing and they also have a decade head start now.
AWS, Google Cloud, Azure etc are not best thought of as datacentre operators. It's the software that makes the cloud. AWS doesn't even operate all their own datacentres. The fact that they do operate many of them is primarily for cost efficiency; they can deliver the same product regardless.
All things considered, I do not see why they couldn't. Much like when Amazon first got into that business, it would likely require them to make some infrastructure changes, hire some people, etc. But there is no logical reason why they could not offer a competitive option.<p>However I do think that from a business standpoint it would feel a bit out of place, or even desperate, for Facebook to get into that space. A more logical approach might be for them to do something more like acquire Wix and allow businesses to have pages that were more dynamic than just a Facebook page. Allow for more direct e-commerce, etc. (and take a cut). If that was successful, they could grow into more datacenter type services as a logical extension.
I highly doubt it as I know other cloud providers smaller than GCP and Azure have trouble with some clients as they want to move to AWS. Cause well the buzzwords.<p>Realistically, Meta doesn't exactly have a great track record with user data and privacy. So I doubt a lot of companies would be willing to join.<p>OVH was created in 1999 and I would say is less well known than AWS probs meta have a similar client to IBM Cloud or OVH.
Why would anyone want that? Personally, I'd like to see some huge collective/co-op form to create an Amazon competitor a TRUE Amazon competitor (all their major profitable verticals -- esp FBA, Fullfillment, and Ecommerce, with AWS just a cherry on top.).
I think they could, at least on a technical level. I don't think they would for business reasons, but there's plenty of smaller companies they could buy up if they didn't want to start from scratch.
Maybe? But do they want to? Here's the thing with being a founder led company: You still think it's your toy, your vision, and you know best.<p>If the goal was to make money, Meta may be interested in cloud computing. Some of the biggest open source projects powering the internet are out of Meta. They have <i>some</i> understanding of developers and know how to interact with them and what they want / need. But alas, cloud computing isn't making the world a more connected place or whatever Zuckerberg thinks he's doing, and until he steps down, the focus required for this type of shift would be difficult to pull off.
I was using Parse until Facebook acquired them in 2013, then abruptly shut down the platform a little over a year later.<p>No, I do not think Meta could compete with AWS.