4 ms·
That's nice, but why would anyone use this instead of Redis, CouchDB or a local database?
by fiatjaf 11y ago
That's nice, but why would anyone use this instead of Redis, CouchDB or a local database?
- willemt 11y agoThe number one differentiator is the small size of the source code. If all you need is a key value server that does GET and PUT, then 1k lines would be easier to understand than +10k. The focus is on doing one thing and doing it well. Compared to Redis, PearlDB has durability for each PUT on by default. Redis doesn't support an HTTP REST interface out of the box. PearlDB's aim is to be a thin layer between the REST interface and the disk. I think this approach should be faster than Redis for durable PUTs, but that still needs to be confirmed through benchmarking. Can't compare to local databases because PearlDB is for setups where distributed nodes need access to a single database.