131–140 of 297 posts
- pouchDB - https://github.com/pouchdb/pouchdb
- RxDB - https://github.com/pubkey/rxdb
- gunDB - https://github.com/amark/gun
- horzion - https://github.com/rethinkdb/horizon
- firebase - https://firebase.google.com/
So the alternative options are: - pouchDB - https://github.com/pouchdb/pouchdb - RxDB - https://github.com/pubkey/rxdb - gunDB - https://github.com/amark/gun - horzion - https://github.com/rethinkdb/horizon - firebase - https://firebase.google.com/
When Parse.com announced it's shutdown I started looking for alternatives but found nothing that could match Parse's simplicity and features.
So I decided to stay with Parse and finally stumbled upon SashiDo.io which made the migration seamless and painless - highly recommended.
Halldor Gislason AGR Dynamics
Why do I feel like this post is getting brigaded by Sashido?
My search for alternatives proved fruitless - there is really nothing that matched the simplicity and power of the light Parse sdk.
After trying a number of solutions I stumbled upon SashiDo.io which has proven to be extremely an excellent choice. The migration has been painless and everything works as well as before or better.
Having full alternative access to the databases is a good bonus as is their excellent service.
Halldor Gislason AGR Dynamics
Earlier quoted context omitted.
> Why do you think Parse was a failure in the first place? Because the title of this post is "Parse.com is shutting down today".
Shutting down is not the same as failure
During this year-long shutdown/migration process, the open-source and community maintained Parse Server is what most people switched to. Parse is yours now. https://github.com/ParsePlatform/parse-server
I loved Parse from the time I first started using it in college. It started out as a really handy way to spin up small apps quickly so I could start beta testing my app quickly with real users. One of the main problems though was that it really felt like just a prototyping tool to me, and I never really used it for real apps in production. Thus, for my latest project that I've been working on for several months now,…
I was wondering if you have a public policy in place which outlines what would happen in the event of a Parse-like shutdown or other end-of-company-life event occurring? I ask in the hopes that it won't be taken as too negative a question but your company is VC-backed in the database space and we've lost a few too many of those this last year.
expecting a vendor to tell you exactly how they're going to fold is something they can surely dream up and send to you so you feel better about the nature of the universe, but something you shouldn't really rely on.
in other words, assume the worst will happen, despite assurances of the contrary.