Why did Facebook decide to shut down Parse?

Re:Why did Facebook decide to shut down Parse? by winslett on Wednesday February 03, 2016 @02:09PM (#11028808)

IMO: Heroku is a bad example of vendor lock in. To use Heroku, no code changes were required which would prevent it from running else where. A counter-argument to my counter-argument, Heroku limitations (i.e. 30-second HTTP request timeouts) required code changes for any and all web apps to work on Heroku. Anyhow, code that runs on Heroku can run anywhere.

Parse, on the other hand, was both the code and the infrastructure.

EDIT: p.s. love your newsletters!

[ Parent | on HN ]

Re:Why did Facebook decide to shut down Parse? by seanwilson on Wednesday February 03, 2016 @02:35PM (#11029050)

> Heroku limitations (i.e. 30-second HTTP request timeouts)

I see this as less of a limitation and more as Heroku forcing you to write your app in a scalable manner. Likewise with Heroku servers/dynos not coming with permanent storage and not letting you SSH into them.

[ Parent | on HN ]