Soul: A SQLite REST and Realtime Server
thevahidal.github.io
Soul: A SQLite REST and Realtime Server
1–10 of 53 posts
Re: Soul: A SQLite REST and Realtime Server
#2I thought the whole point of sqlite is that you don't have to deal with the cruft and overhead of having to send queries over a network connection. Why tack that back on?
Re: Soul: A SQLite REST and Realtime Server
#3I thought the whole point of sqlite is that you don't have to deal with the cruft and overhead of having to send queries over a network connection. Why tack that back on?
To me whole db being a single file is something.
Re: Soul: A SQLite REST and Realtime Server
#4I thought the whole point of sqlite is that you don't have to deal with the cruft and overhead of having to send queries over a network connection. Why tack that back on?
That's a great question. This pattern is actually getting popular today with services like Turso and Cloudflare D1 (technically only SQLite compliant).
There are a few reasons I can see reaching for SQLite behind an API rather than something like Postgres. Portability can be a big benefit and I would expect you don't need to deal with connection pooling.
If I had a service running on a single box and didn't mind setting up my own db backups, I might reach for SQLite just for the ease of standing up new environments for dev and automated testing.
Re: Soul: A SQLite REST and Realtime Server
#5I thought the whole point of sqlite is that you don't have to deal with the cruft and overhead of having to send queries over a network connection. Why tack that back on?
Accessing the database from multiple applications or systems.
SQLite is great for sharing application data as well. If you have, for example data for a specific event,. It can make sense to use a separate database/file.
Being able to simply copy as a backup/archive is big here.
You might still want your application or services separate. Similarly take a look at Turso or AstroDB for more options. Turso created libSQL as a fork with libSQL server.
Re: Soul: A SQLite REST and Realtime Server
#6I thought the whole point of sqlite is that you don't have to deal with the cruft and overhead of having to send queries over a network connection. Why tack that back on?
Frankly, you thought wrong. The whole point of sqlite was to build a database for naval vessels. Aside from that, given it's open source, the "point" of it doesn't really matter anymore.
Re: Soul: A SQLite REST and Realtime Server
#7I thought the whole point of sqlite is that you don't have to deal with the cruft and overhead of having to send queries over a network connection. Why tack that back on?
Frankly, you thought wrong. The whole point of sqlite was to build a database for naval vessels. Aside from that, given it's open source, the "point" of it doesn't really matter anymore.
Huh, this is a little piece of history I was not aware of. Neat and somewhat helps explain the design philosophy of SQLite knowing that
Re: Soul: A SQLite REST and Realtime Server
#8Some suggestions:
The submitted page can add a link to the github repo. If it is already there it isn't obvious.
As the links to /api/tables and others are throwing 404, I had to copy & paste the url from the dev snippet to see examples of the API.
Running the server to view documentation helps in ensuring that the docs are current but it will also add unnecessary friction and deter those who want to just look at the API doc for evaluation.
PS: The source url is https://github.com/thevahidal/soul
Re: Soul: A SQLite REST and Realtime Server
#9Earlier quoted context omitted.
Frankly, you thought wrong. The whole point of sqlite was to build a database for naval vessels. Aside from that, given it's open source, the "point" of it doesn't really matter anymore.
Huh, this is a little piece of history I was not aware of. Neat and somewhat helps explain the design philosophy of SQLite knowing that
Semi-related, there’s an anecdote that the InterBase database was selected for use within the M1 Abraham’s tank because it was particularly robust in its implementation.
Apparently an issue with the M1 is that because of the energy produced when the main gun is fired, internal systems may spontaneously reset. So they had to design around that phenomenon through things like robustness and rapid system restart times.
Re: Soul: A SQLite REST and Realtime Server
#10Earlier quoted context omitted.
Frankly, you thought wrong. The whole point of sqlite was to build a database for naval vessels. Aside from that, given it's open source, the "point" of it doesn't really matter anymore.
Huh, this is a little piece of history I was not aware of. Neat and somewhat helps explain the design philosophy of SQLite knowing that
If you want to know more of the origins of SQLite I can highly recommend this episode of the Corecursive podcast