Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

github.com

Post reply on HN
Print view View original

11–20 of 66 posts

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#11

Post by edraferi »

mtolan wrote: post #7

I think your title might not be the best; * Serverless typically implies something accessible from more than the host you're on * It's not zero configuration, there's at least 1 configurable parameter (albeit with a sensible default) * I'm actually not even clear why this is a document store limited to JSON, other than you're piping it though a JSON python module. Having done some things like this in the past, as you…

I agree that "serverless" now mainly means "Function as a Service." The goal here is convey that there is no server component of the database, similar to SQLite and unlike PostgreSQL.

What is the correct terminology to highlight this architectural distinction?

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#13

Post by hashkb »

pmelendez wrote: post #9
sigmonsays wrote: post #6

This is 200 lines of bash using the file system as a database. The term document store implies a database which this is not. How is this different than just writing files to a directory? What are the use cases of this project?

"A database is an organized collection of data". I think writing files in a directory with a convention falls in that category. [1] https://en.m.wikipedia.org/wiki/Database

Missing the point on purpose?

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#14

Post by hashkb »

edraferi wrote: post #11
mtolan wrote: post #7

I think your title might not be the best; * Serverless typically implies something accessible from more than the host you're on * It's not zero configuration, there's at least 1 configurable parameter (albeit with a sensible default) * I'm actually not even clear why this is a document store limited to JSON, other than you're piping it though a JSON python module. Having done some things like this in the past, as you…

I agree that "serverless" now mainly means "Function as a Service." The goal here is convey that there is no server component of the database, similar to SQLite and unlike PostgreSQL. What is the correct terminology to highlight this architectural distinction?

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-configuration JSON document store

#15

Post by rad_gruchalski »

nodesocket wrote: post #4
CJefferson wrote: post #3

If you are going to invoke the sacred name of 'sqlite', then I expect to see rock-solid code and quality testing. Instead, there are two tiny tests, and I found a couple of issues in 30 seconds of looking at the code. EDIT: I should prove my point. 1) Race condition on calculating uuid (obviously won't be too serious for a good uuid implementation) 2) No check that file is written successfully. 3) No check when json…

Create some issues and pull requests and help out. :-)

How about some due diligence first? I know, it's so easy to say "just create a pull request". To which the answer is: "I'm not going to use your software if you can't make effort to test it and document properly".

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#16

Post by camus2 »

nodesocket wrote: post #8
mtolan wrote: post #7

I think your title might not be the best; * Serverless typically implies something accessible from more than the host you're on * It's not zero configuration, there's at least 1 configurable parameter (albeit with a sensible default) * I'm actually not even clear why this is a document store limited to JSON, other than you're piping it though a JSON python module. Having done some things like this in the past, as you…

There is already an issue about supporting sharding https://github.com/nodesocket/jsonlite/issues/15 .

I thought it was "serverless"? what does "sharding" have to do with anything? I'm sorry but it seems like you throw around some vocabulary that doesn't describe your project properly, to make it look bigger than it really is. That's nice marketing but it does not feel like there is much effort put into it, when I looked at your bash script.

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#18

Post by camus2 »

pmelendez wrote: post #9
sigmonsays wrote: post #6

This is 200 lines of bash using the file system as a database. The term document store implies a database which this is not. How is this different than just writing files to a directory? What are the use cases of this project?

"A database is an organized collection of data". I think writing files in a directory with a convention falls in that category. [1] https://en.m.wikipedia.org/wiki/Database

The point is the project seems a bit low-effort. The most complicated thing in that bash script is argument processing.

What is the added value of that project? does it come up with something new or interesting? a query language for data? an efficient data storage? no, it just store json files in directories. Sure the file system is already a database, but that project doesn't add anything to the file system.

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#19

Post by noonespecial »

Hint: If you really want to use your filesystem as a database (and don't mind the haters, there's a long and storied history of doing just this), make sure you break it up into many subdirs usually based on the first few characters of the uuid.

Example: ./jasondir/aa/bb/cc/aabbccdd

You won't like what happens when you put 100k files in one directory.

Re: Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

#20

Post by TheGreatPotatoe »

noonespecial wrote: post #19

Hint: If you really want to use your filesystem as a database (and don't mind the haters, there's a long and storied history of doing just this), make sure you break it up into many subdirs usually based on the first few characters of the uuid. Example: ./jasondir/aa/bb/cc/aabbccdd You won't like what happens when you put 100k files in one directory.

There was an old document management system called Keyfile that did just that.
Post reply on HN