[Jare]

> in ~2 hours, you can get the open source Parse clone they released going and be back to new

I keep hearing this, and I have a hard time believing it. Are there any examples of a significant app/developer doing this? Sure a working Parse Server is easy to get up and running, but the reason someone wouold choose Parse was to avoid operations, and that's not a service you build in your company in 2 hrs. (as an aside, it looks to me like the Parse Server is a very limited subset of the real Parse)

[lacker]

If you have a small app and don't need to be careful about scaling issues, then 2 hours is pretty accurate I think. It's trickier when you have a large app, because with Parse Server you do need to handle your own databases and production environment. So I think some of the larger apps are either going to need to hire some devops folks, or make an arrangement with higher-service providers like ObjectRocket.

It has been less than a week, though, so we will see.

[arihant]

Parse Server uses Mongo, there are plenty of operations-free Mongo hosting options, like Compose. Also, Parse server code itself could be given to company such as Heroku or AWS beanstalk to host it for you.

[campers]

There's quite a few pieces missing from the open source Parse server. https://parse.com/docs/server/guide#migrating Analytics, Push (a big one), Config, Jobs. I've been building a mobile app platform on Parse for a while, so I'll have to re-build all the missing pieces for all my existing customers and to keep the new customers coming in. Its something I'd been planning/researching for a while for the next version anyway, the number of times I've said fcuk Parse! Now I have to hurry up and build the next Parse anyway at http://appstack.systems

[semerda]

If someone wrapped it as a microservice with containers and a deployment script for AWS then yes. Otherwise the configuration alone would take few hours. This then begs the question; was/is AWS or Google a better backend to rely on long term.