HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
syamdanda
jsonbase
JavaScript2020–2020
syamdanda / jsonbase

jsonbase

A database software completely built as JSON files in backend. A powerful, portable and simple database works on top of JSON files. It is like a database software, currently having basic CRUD operation features. You can use this as a backend for your ReST APIs as well. The software is completely free and opensource. We are coming up with new features and providing more updates. The another beautiful advantage with JSON-base is since it is a NPM module, this fits well in your nodeJs applications eco system. if you want to develop quick prototypes/poc or need of a database with minimal requirements then, JSONBASe is an must option that you can consider. However there is a limitation if you go beyond a million records per table.

3Distinct people
3Mentions
0Explicit recommenders
561GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A database software completely built as JSON files in backend. A powerful, portable and simple database works on top of JSON files. It is like a database software, currently having basic CRUD operation features. You can use this as a backend for your ReST APIs as well. The software is completely free and opensource. We are coming up with new features and providing more updates. The another beautiful advantage with JSON-base is since it is a NPM module, this fits well in your nodeJs applications eco system. if you want to develop quick prototypes/poc or need of a database with minimal requirements then, JSONBASe is an must option that you can consider. However there is a limitation if you go beyond a million records per table.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2020-07-02 17:19:30 UTC to 2020-07-03 04:46:12 UTC.

012020-07-02 17:00:00 UTC to 2020-07-02 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 2, 17:002020-07-02 18:00:00 UTC to 2020-07-02 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-02 19:00:00 UTC to 2020-07-02 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-02 20:00:00 UTC to 2020-07-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-02 21:00:00 UTC to 2020-07-02 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-02 22:00:00 UTC to 2020-07-02 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 2, 22:002020-07-02 23:00:00 UTC to 2020-07-03 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-07-03 00:00:00 UTC to 2020-07-03 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-03 01:00:00 UTC to 2020-07-03 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-03 02:00:00 UTC to 2020-07-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-03 03:00:00 UTC to 2020-07-03 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-03 04:00:00 UTC to 2020-07-03 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 3, 04:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 2, 17:002020-07-02 17:00:00 UTC2020-07-02 18:00:00 UTC110
Jul 2, 18:002020-07-02 18:00:00 UTC2020-07-02 19:00:00 UTC000
Jul 2, 19:002020-07-02 19:00:00 UTC2020-07-02 20:00:00 UTC000
Jul 2, 20:002020-07-02 20:00:00 UTC2020-07-02 21:00:00 UTC000
Jul 2, 21:002020-07-02 21:00:00 UTC2020-07-02 22:00:00 UTC000
Jul 2, 22:002020-07-02 22:00:00 UTC2020-07-02 23:00:00 UTC000
Jul 2, 23:002020-07-02 23:00:00 UTC2020-07-03 00:00:00 UTC101
Jul 3, 00:002020-07-03 00:00:00 UTC2020-07-03 01:00:00 UTC000
Jul 3, 01:002020-07-03 01:00:00 UTC2020-07-03 02:00:00 UTC000
Jul 3, 02:002020-07-03 02:00:00 UTC2020-07-03 03:00:00 UTC000
Jul 3, 03:002020-07-03 03:00:00 UTC2020-07-03 04:00:00 UTC000
Jul 3, 04:002020-07-03 04:00:00 UTC2020-07-03 05:00:00 UTC101

What Hacker News says

3 sources
You definitely shouldn't use this in production. Looking at the code there's: - race conditions everywhere. - bad and inconsistent formatting, which doesn't help with the - huge if-else monstrosities. - Also uses synchronous IO and asynchronous IO randomly. - Uses try-catch liberally, doesn't check the caught errors, and just re-tries blindly forever in some cases. If you do any parallel updates/inserts/removals with this "database" you're pretty much guaranteed to lose data. Updates are essentially: 1. read table, 2. make changes, 3. save table. Which at least would work if it was all synchronous. I know this is going to sound harsh, but building databases is hard for even the most experienced coders, and whoever wrote this is clearly at the other end of that spectrum. https://github.com/Devs-Garden/jsonbase/blob/master/tables.j...
In Json-Base – Database built as JSON files

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.