On the Lobsers feed there was an item about GoatDb. And it is a database in the NoDB group. It is the first time i read the term. Curious as I am I tried to find information about NoDB.
I found a Python NoDB, a .NET NoDB, a github NoDB topic, a paper about queries on raw database files and an article about event sourcing.
From that information I got a grasp on what NoDB means.
Lets take a step back and look at what databases are. There are two big parts in a database; the query engine and the storage. The query engine decides how the information is stored. Most databases store data in a binary file, because it is smaller.
And that is where the no part of NoDB comes in. Instead of the query engine picking the storage format NoDB is using plain data files as storage. Although I have seen solutions that use a spreadsheet. So at what point NoDB becomes db?
The main benefit I see is that as a developer you can manipulate the data bypassing the query engine. When you have a more efficient way to store the files you can implement that and use the query engine only to retrieve information.
Would i use it? With all the different database solutions that exist, I would go for a document store database first before I go for a NoDB solution.
What are your thoughts?
Top comments (0)