Platform · 2011–2017 · Cloud Scale
Parse
BaaS before Firebase owned the category. Open-sourced on the way out; trust never recovered.
Why Parse faded
Parse faded because platform risk became a lesson when Facebook pulled the plug. Teams learned that backend-as-a-service without an exit plan is a ticking migration. Firebase inherited the market with better Google balance-sheet optics — same risk, different logo.
Cost of the fad
What Parse cost
Facebook shut down Parse with a year's notice, forcing thousands of mobile backends into emergency migrations or self-hosted forks.
Case studies
Patterns
Compare with
Related
Platform · 2014–now
Firebase
Auth, realtime DB, and hosting as a product. Prototype paradise; vendor lock purgatory at scale.
Platform · 2009–now
MongoDB
Document DB that became a punchline, then a grown-up product. Survived by getting serious about transactions and ops.
Practice · 2010–now
Mobile-first / Responsive
Design for the small screen first. Became table stakes, not a differentiator.
Platform · 2007–2023
Heroku
git push deploy and twelve-factor bliss. The PaaS that taught a generation what deploy should feel like — then priced them out.
$ Free-tier sunsetting and Salesforce neglect sent hobbyists and startups shopping mid-project. Dyno pricing that made sense at demo scale became a line item at traction.