3 ms·
Killing of Parse definitely showed that Facebook didn't want to be in PaaS/IaaS. Now, there's going to be severe trust issues with any PaaS/IaaS with a Facebook
by Abishek_Muthian 7y ago
Killing of Parse definitely showed that Facebook didn't want to be in PaaS/IaaS. Now, there's going to be severe trust issues with any PaaS/IaaS with a Facebook branding.
Parse was ahead of its time, good Engineering, nice documentations and possible the first platform to make building backend/database system for an app seamless. Even when Facebook killed it, they did a great job at open-sourcing the platform.[1]
I had migrated my existing services to open-source Parse and even built a stateless application with >250,000 users with it few years back. But if I had to build the same backend now, I'll probably do it with Go/pgSQL instead of NodeJS/MongoDB as in Parse.
[1]https://parseplatform.org/ https://parseplatform.org/
- mst 7y agoI mean, yes, but also a reputation for killing things off hasn't entirely stopped people from using GCP.
- Abishek_Muthian 7y agoI should have been more clearer, FB's reputation loss is not just from killing things!
- weare138 7y agoHonestly this was the first thing I thought when I read the headline. No one using enterprise cloud services is going to trust Facebook with their data and mission critical systems.
- lowdose 7y agoWell Google has invested more than $30 billion in the could last 3 years. This wait until Google is going to pull the plug is getting a bit annoying. I welcome the competition with AWS.