3 ms·
We shipped an app last year with Realm and are in the process of migrating off of it—it just wasn't reliable enough. We regularly saw crashes deep in their libr
by erichocean 10y ago
We shipped an app last year with Realm and are in the process of migrating off of it—it just wasn't reliable enough. We regularly saw crashes deep in their library with highly concurrent usage. Extremely frustrating.
Adding something complex like OT on top of Realm's existing foundation would make me even less likely to use it in the future.
That said, it's nice to see them tackling the problem and I wish them the best. Obviously, bugs can be fixed given enough time and effort and in principle, I like their product.
- bigfish24 10y agoWe really value this honest and direct feedback. Thank you for telling your experience. Obviously, we would love to change your mind and we will continue to improve the database and server product to hopefully earn that in the future.
- brmunk 10y agoReally sorry to hear you had a bad experience! I assume you created an issue for it? If not I would love to hear more about it (bm at realm dot io), so we can get it fixed and hopefully get you back as a happy camper again at some point. Obviously one of the main points of building the new sync solution (or any library really) is to give you much more time for building differentiating features rather than building basics yourself. Now granted there are other solutions for the pure local persistence, but not many - if any - that will do what the new Realm Mobile Platform will for solving sync. But obviously the basics must be right and solid - so hope you will provide us with sufficient info so we can get any of your issues resolved.