Live data from Hacker News

Soul: A SQLite REST and Realtime Server

thevahidal.github.io

51–53 of 53 posts

Re: Soul: A SQLite REST and Realtime Server

#51
post #12

Earlier quoted context omitted.

>I 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? An interesting application could be a web-application whose ONLY server is the SqLite -server. The state of the application would be stored into the SqLite database, not into "local storage" etc. Using a relational database is a great improvement i…

What’s the security model for this? Seems like you’d end up with users able to run arbitrary queries against the database.

Good Question. The SqLite REST-server should probably provide ways of allowing only selected operations. There's no reason why EVERYTHING should be possible over the network.

One possibility could be that each user would have their own copy of the database, let them break it if they want to :-)

Re: Soul: A SQLite REST and Realtime Server

#52
post #42

Why SQLite? Why not provide a generic SQL interface? I never understood that. Why do people build this around SQLite?

Seems like a toy solution, sqlite is the easiest to set up for someone who isn't familiar with databases

The fact is sqlite and its derivatives are more than enough for a LOT of the web lol, people always act like their random site needs 10,000qps to operate when in reality most barely crack 5-10

Re: Soul: A SQLite REST and Realtime Server

#53

I am not sure what Realtime means here. But if it means something close to what I used to [1], then REST is a horrible idea. Javascript is not a good idea either. [1] " Real-time computing (RTC) is the computer science term for hardware and software systems subject to a "real-time constraint", for example from event to system response.[1] Real-time programs must guarantee response within specified time constraints, o…

Realtime seems to mean - in this context - that you can open up a web socket and subscribe to changes to rows. i.e. get changes to rows pushed to you as a client instead of pulling.

Yes basically the meaning of "realtime" in databases, not the realtime of RTC :S
Post reply on HN