Oh definitely. This is a fine example of how to do a service shutdown. Sadly, I await the comments from unprepared customers next year.

If you make apps and use any sort of {P,B,S,I,}aaS, do you yourself a favor and follow/subscribe/whatever to their news/release channels.

Yes! I wrote about this a few years ago:

http://geekestateblog.com/monitoring-microvendors/

It's really important as people build apps (and business value) through composition of smaller services rather than composition of code that they become aware of these external dependencies. And not just at build time, but during the operation of these apps/business processes.

I just received an email informing me of the shutdown

also major props for being up-front about the fact that they're shutting down the service and they realise it sucks for their users, rather than some "incredibly journey" style bs.

From the original post:

> We have a difficult announcement to make.

Yes, you can see their sheepishiness in the announcement.

I'm sure it was a tough decision.

Is it an open source release of the core Parse product? I am genuinely curious, hence the question.Correct me if I am wrong, but this means that most of their product is the Parse server and whatever migration tools they used to store data for users.

I hope we will see a lot of migrating tools and blogs

We are working on this @Hasura.io. This is our blogpost in response to the Parse shutdown. https://news.ycombinator.com/item?id=10994104