Filesystems are databases. Do we use filesystems because they're faster than doing direct i/o?
There isn't a value proposition for databases, because a value proposition is a business statement. If there were a business statement for databases, it would be a management interface for data. Nobody cares if a database is fast, they care if they can get their data in and out easier.
This is just bunch of vacuous statements. Are you suggesting this product exists not to serve a business prop or value ?
> Nobody cares if a database is fast
Businesses do. There’s a reason people don’t attempt to build their own database.
Every serious database meant for production use takes performance into consideration. People would just roll their own database otherwise, but we pile into Postgres, or even MongoDb, because they’re are battletested and has had years of optimizations. More than half of the work in database implementations is in engine and query optimization.
> they care if they can get their data in and out easier.
Then just store and read flat files from disk.
Strange to use a throwaway to make this comment. It seems like you are the author justifying a product that does need to exist.
The main value prop of a DB is performance, moreso than the interface. How is this different from S3 or Firebase’s rest API?
> Nodb can easily accommodate an increase in the number of requests without breaking down or becoming slow. Your app remains responsive and reliable, even during periods of high demand.
From the limitations docs page:
> Number of read (GET) requests is limited to 10k per month