That’s interesting. My spare time tinkering is around offline first embedded querying/storage with more of a focus on operational data (in particular spatial/spatiotemporal). Most of the big offline use cases I’ve seen are aerospace/drones or logistics or robotics where they want to juggle a lot of things at once concurrently (normally by stringing together a few different things currently). Most of the time I mention it people just terminate the conversation at SQLite or DuckDB when they don’t really fit for the hot path of any of most operational use cases or jump straight to the big cloud DBMS du jour.
> When you need the same database to be running on mobiles and servers alike, you need embedded database for mobile and standalone executable for server.
Most of the people I’ve run into just want some sort of replication system that’s a bit richer than MQTT et al.
> No amount of coordination with the storage engine can override the physics of lock contention in distributed systems.
Carrying on from the previous point. Distributed querying may still just be a workaround rather than something anyone actualy wants to do as a first option.
> When you need the same database to be running on mobiles and servers alike, you need embedded database for mobile and standalone executable for server.
Most of the people I’ve run into just want some sort of replication system that’s a bit richer than MQTT et al.
> No amount of coordination with the storage engine can override the physics of lock contention in distributed systems.
Carrying on from the previous point. Distributed querying may still just be a workaround rather than something anyone actualy wants to do as a first option.
That’s cool either way Enjoy