Now this is an interesting concept. I spent a few weekends writing a postgres proxy for PII a few years ago and I realized how much you really could inbetween a database and your app layer.
Never thought about just leveraging sqlite as the entire backend and running every database protocol as its interface.
I like the concept, but I don't quite get what problem specifically this is trying to solve or what the main motivation here is. Have an all-compatible database that is essentially just SQLite plus some scripts?
Also those AI coded CSS gradient backgrounds got old really really fast. It kind of became a low quality indicator like Word Art or Comic Sans back in the day: You see it and immediately have a thought like "Oh, it's one of those." in your head. At least that's the case for me and basically everyone in my tech bubble ...
Third-party audits like https://jepsen.io/ are an example.
README doesn't mention anything about how transactions work across the shards.
I see this https://github.com/schapman1974/briskdb/pull/260 but it says shard-local.
Never thought about just leveraging sqlite as the entire backend and running every database protocol as its interface.
Also those AI coded CSS gradient backgrounds got old really really fast. It kind of became a low quality indicator like Word Art or Comic Sans back in the day: You see it and immediately have a thought like "Oh, it's one of those." in your head. At least that's the case for me and basically everyone in my tech bubble ...