Over a million developers have joined DZone.

While I Will Miss Parse, I Wish Every Service That Shutdown Left Behind The Same Page

Parse is shutting down and will be missed by many. However, their resources for running an open sourced Parse backend on your own server, and migration info sets an example for other services on how to properly shut down.

· Mobile Zone

It definitely sucks that Parse went away like they did, but you have to commend them on the page they left behind. Facebook put up the download link to an open source version of Parse Server, and a link to the migration guide. I like that they also left up the blog, (which I think is almost just as important as the code), telling the story of what happened right up to the end.


I come across newly deprecated API providers and API service providers all the time. Most of the time they are just dormant with nothing going on but a site, and other times the website is just gone with no message at all. I rarely ever come across anyone who puts up an open source version of their platform with instructions on what to do next and leave the blog up.

If you are running an API or a service that caters to the API space and you are facing shutting everything down, feel free to reach out. I'm happy to put up a splash page, help organize a Github repo of any server and client code, as well as your API definitions. I'm happy to pay for the domain so that the work you did doesn't go away, and people can learn from and in some cases build off of what you did. 

Topics:
parse.com ,shutdown ,backend ,backend as a service ,baas ,parse ,mobile

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}