SQLedge uses Postgres logical replication to stream the changes in a source Postgres database to a SQLite database that can run on the edge. SQLedge serves reads from its local SQLite database, and forwards writes to the upstream Postgres server that it’s replicating from.
This lets you run your apps on the edge, and have local, fast, and eventually consistent access to your data.
Should be much faster for reads than hitting the full PSQL DB, but lacks features like aggregation and triggers. Wonder if this could be incorporated into Lemmy for any benefit.
Sqlite can be super useful for client side caching, searching and filtering. But this would require having you’re postgres database exposed to your end users. That would be a huge security mistake unless your users are all internal and trustworthy. Definitely retrieve data over an API instead.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Sqlite can be super useful for client side caching, searching and filtering. But this would require having you’re postgres database exposed to your end users. That would be a huge security mistake unless your users are all internal and trustworthy. Definitely retrieve data over an API instead.