People are really going to be cranking out entire databases in a weekend that no one is going to use. Why even make the effort, if you can even call it that? It would be one thing if the software was actually beneficial, as it would be undeniably useful and the fact that it took a weekend to make is of no importance. But databases are extremely complicated and require high levels of trust since they actually store important information. No one would care if you made a terrible AI-generated winamp clone that couldn't play music correctly. There's no consequence. But who would use and trust a database if the author didn't even understand it enough to make it? If you made this 5 years ago I would probably be interested and looking through some of the code. These days weekend projects aren't even worth a second thought.
I did. Distributed too and supports erasure coding. The reason is because nothing quite had the architecture or features I wanted in a deployment pattern that matched my use case. All major databases that are validated are complicated to operate. I built something that operates one way for a non business use. It’s great, doesn’t need to serve a million people, just about 5 or so. Doesn’t need to be the most optimized thing ever.
I’m opting out of any corporate targeted code for personal use, anything not designed for user experience gets scrapped when I’m the user and I have Software on Demand as a Service.
Fantastic stuff. I love this trend of pushing SQLite for advanced scenarios and new architectures. It’s so much more powerful than people give it credit for.
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.
egregious AI slop. you even had your LLM generate you a "launch kit" [0] with posts for HN, multiple subreddits, Linkedin, and X, with a four-week recommended posting schedule.
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 ...
It’s an interesting set of features. I’m not one of the gatekeepers of AI projects are bad ilk. Let’s see this keep growing into what you have in mind OP.
Don't be discouraged by some of the comments on this thread. Looks like you had an interesting idea and you implemented it and now you are sharing your work. You have stated that it is alpha.
Personally, I don't care if was written by AI or by 12 drunken monkeys -- if it has a sufficient level of testing (high bar here!) that shows that it reliably and safely does what it is intended to do -- that is all that really matter.
I'm interested in the social-proof mechanisms we'll need to have for AI-assisted "serious projects" (where a database is a "serious project").
Third-party audits like https://jepsen.io/ are an example.
101 commits. First on August 7th. I don't consider this a serious project.
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.
People are really going to be cranking out entire databases in a weekend that no one is going to use. Why even make the effort, if you can even call it that? It would be one thing if the software was actually beneficial, as it would be undeniably useful and the fact that it took a weekend to make is of no importance. But databases are extremely complicated and require high levels of trust since they actually store important information. No one would care if you made a terrible AI-generated winamp clone that couldn't play music correctly. There's no consequence. But who would use and trust a database if the author didn't even understand it enough to make it? If you made this 5 years ago I would probably be interested and looking through some of the code. These days weekend projects aren't even worth a second thought.
I did. Distributed too and supports erasure coding. The reason is because nothing quite had the architecture or features I wanted in a deployment pattern that matched my use case. All major databases that are validated are complicated to operate. I built something that operates one way for a non business use. It’s great, doesn’t need to serve a million people, just about 5 or so. Doesn’t need to be the most optimized thing ever.
I’m opting out of any corporate targeted code for personal use, anything not designed for user experience gets scrapped when I’m the user and I have Software on Demand as a Service.
Fantastic stuff. I love this trend of pushing SQLite for advanced scenarios and new architectures. It’s so much more powerful than people give it credit for.
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.
egregious AI slop. you even had your LLM generate you a "launch kit" [0] with posts for HN, multiple subreddits, Linkedin, and X, with a four-week recommended posting schedule.
0: https://github.com/schapman1974/briskdb/pull/264/files#diff-...
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 ...
It’s an interesting set of features. I’m not one of the gatekeepers of AI projects are bad ilk. Let’s see this keep growing into what you have in mind OP.
This is very cool!
Don't be discouraged by some of the comments on this thread. Looks like you had an interesting idea and you implemented it and now you are sharing your work. You have stated that it is alpha.
Personally, I don't care if was written by AI or by 12 drunken monkeys -- if it has a sufficient level of testing (high bar here!) that shows that it reliably and safely does what it is intended to do -- that is all that really matter.
“ Why developers might care”
This phrase makes it sound like the author wasn't, himself, a developer. Like, maybe he wasn't even human.
Looks like another art project.
[dead]