Ask HN: Mobile-first” databases that sync to a central server?

[saurabhnanda]

I keep hitting the following problem over & over again:

- Build a mobile app (mostly some sort of CRM/ERP kind of app), where ALL the features need to work offline - This means that all the data (for the currently logged-in user) needs to reside on the mobile device. - This also means that any CRUD operation needs to hit the local data-store first, and should be synced in the background with a remote data-store. - This also means that if the user signs into another mobile device, a relevant subset of the remote datastore should be "restored" on the mobile device. - Probably a few other subtleties that I haven't thought through yet.

Is there any stable/production-grade DB that solves this problem? Bonus points if it's an RDBMS, because building reports for a CRM/ERP is 10x easier on top of an RDBMS vs a document/JSON DB.

[gt565k]

Sybase MobiLink does this. It has a central sync server that manages syncing data between a RDBMS and the phone's database. It got bought by SAP and might have been deprecated.

https://help.sap.com/viewer/4949f39728bd400ebee2fb94687cc74f...

[gt565k]

better link

SQL Anywhere (mobilink is the service for syncing mobile data/remote)

https://www.sapstore.com/solutions/99017/SAP-SQL-Anywhere

[auganov]

I've worked on (and actively promoted) products in this space but nowadays I'm rather disillusioned with the dream of effortless sync. It works pretty well in dev. But once you have to deal with aggregations and security it all falls apart. You end up having to reinvent a regular backend in a very convoluted way on top of a second-rate db. It's like all the problems with ORM but on steroids.

[simplerman]

I tried to build this for my MVP which was also CRM. I stopped for other reasons, but this is how I was doing:

1. Store data locally in SQLite.

2. Export from DB to JSON string.

3. Encrypt JSON with in memory password.

4. Save encrypted string on backend server running Laravel and MySQL.

Basically, I provided backend only for sync functionality. And I liked that data was encrypted on client, so I had less liability.

[LarryMade2]

I've done one with a LAMP stack on android with a distributed DB setup you got the varsatility of PHP and all the libraries you need. The challenge is if you want the client not to have local code.data access and to have confident security setup for updating from a remote app to the server.

[steerpike]

I've tried to find something similar and as far as I can tell the best current candidate available is pouchdb syncing to a couchdb instance.

If offline first isn't a must have and you're ok supporting 'intermittent offline' then Firestore with offline enabled is probably your simplest option

[UK-Al05]

I don't know but you would have to work out how to resolve conflicts as well. So you would need something like a version vector or vector clock.

[avinassh]

Have you looked into Realm? It might fit your use case

[0] - https://realm.io/

[jsilence]

also interested in this with a different use-case. We'd like to have agricultural applications 'offline first' so that they always work no matter whether connectivity is there or not.