[lacker]

Hey, I'm sorry to hear that. I know it's really frustrating when you rely on a service that closes down. I'm curious - can you not afford to change it because it's too much work, or can you not afford to change it because the alternatives are too expensive? Maybe there is a way forward that is not as bothersome as you expect.

[schwarrrtz]

I'm involved in a project that uses Parse, and by this point the client SDKs are so thoroughly embedded into our codebase that changing to another backend system would indeed be a fair bit of work. Apparently modular design is a thing.

Fortunately, Parse has provided us with more advanced warning and open-source support that I could ever have expected. This is consistent with my experience using the service; you probably don't remember, but you personally responded to a tweet I sent regarding an outage, and followed up to make sure that the issue was resolved for me.

Many thanks to you and your team for all your hard work.

[lacker]

Well the nice thing with this migration is that you don't have to rip out the client SDKs. After migrating the backend to the open source stuff, you just have to change the serverURL and you can point the same mobile app to the new backend.

Thanks for your kind words ;-)

[schwarrrtz]

Yup! And hosting the Node server on Heroku/MongoLab should be a reasonable solution, especially if the open source community takes this and runs with it.

[bijbij]

I just want to say it is not fair when you have done something for your clients after some years they tell you it does not work.

It will get some more time from me or money from my client to get around setting up a server moving data to it find and change the url or probably fixing server mis config.

They will take it as my mis responsibility.

I would not use their service for my client if I know it going to close that at first place.

The last but not the least I can not figure out why fucking hacker news down vote me for 4 points.