Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by hashkb on Sunday February 12, 2017 @09:35AM
(#13628482)
SQLite is a library. If you call a program to store your data, it's a DB server. Same host or not.
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by tyingq on Sunday February 12, 2017 @11:05AM
(#13628934)
"daemonless" makes the most sense to me, though I doubt that would catch on.
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by cocktailpeanuts on Sunday February 12, 2017 @03:28PM
(#13630532)
Of course there is no server, since we are talking about local. I agree with others that the title is misleading. I looked at the project for a while to realize that it's just a local command line interface to storing objects in sqlite.
While I am sure there are use cases for this, it is not correct to say this is "serverless".
By that standard you can call literally ANYTHING "serverless".
For starters, this coffee I'm drinking right now is "serverless". It does its job well, completely without a server!
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by deif on Sunday February 12, 2017 @11:38AM
(#13629080)
What's wrong with 'local'? Serverless is a terrible word to describe this.
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by evanweaver on Sunday February 12, 2017 @12:16PM
(#13629289)
I always thought they were "embedded" databases.
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by phamilton on Monday February 13, 2017 @01:45PM
(#13637656)
"embeddable datastore" is the right term
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by jeshan25 on Monday February 13, 2017 @03:28PM
(#13638458)
your headline is good except the term "serverless".
please drop it.
The term means much more than "not hosting it on a server". As somebody pointed out, "embedded datastore" may be a better term.
Re:Show HN: JSONlite – A simple, serverless, zero-configurat...
by mjn on Monday February 13, 2017 @03:32PM
(#13638482)
I agree the term is confusing now that "serverless" has a cloud-related definition, but in the database world, it is traditionally one of the terms used as an antonym to "client/server database". See, for example: https://sqlite.org/serverless.html
What is the correct terminology to highlight this architectural distinction?