There are some inherent issues with Baas providers .The biggest of them is the low reward for maintenance. Big players in the application sector are already self reliant with strong backend infrastructure and its the low market cap count indie developers who are adopting these services .
Facebook backing out seems the biggest testament to the fact. I myself have been using Parse for my application - play.google.com/store/apps/details
The data being served from there is the application category for apps installed on a user device .
The parse announcement did come as a shock to me but i was prepared because (may not apply to everyone) i was going to open source the app anyways after a year of maintenance and also release the data publicly . (The parse data)
Coming to parse itself . It had won me over with its beautifully written documentation and absolutely no frills written API . I am thankful to the team for serving so many clients with minimum downtime and also releasing the source code for parse server api , and a substantial time and documentation for migration
I would totally agree with @JanVladimirMostert for the point he raised . Trusting a service like this is an absolute no brainer when it comes to making production ready code waiting to scale up , but the thing that struck me most was , the parse team was so enthusiastic after the facebook acquisition that it almost meant that they would never die out . But sadly that did happen and there is nothing that you can do to help yourself other than migrate to other Baas like firebase or aws mobility or simply write up your own scaleable infra :)