diff options
Diffstat (limited to '_posts/2020-08-31-the-database-i-wish-i-had.md')
| -rw-r--r-- | _posts/2020-08-31-the-database-i-wish-i-had.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/_posts/2020-08-31-the-database-i-wish-i-had.md b/_posts/2020-08-31-the-database-i-wish-i-had.md index 3ffbb6c..1732429 100644 --- a/_posts/2020-08-31-the-database-i-wish-i-had.md +++ b/_posts/2020-08-31-the-database-i-wish-i-had.md @@ -24,7 +24,7 @@ long for a database with a certain set of values, and for a few years I was just waiting for someone to finally write it. After watching his talk, Bryan is saying to me: "time to stop waiting, and start writing it yourself". -So let me try to give an overview of such database, and go over it's values. +So let me try to give an overview of such database, and go over its values. ## Overview @@ -63,7 +63,7 @@ that would have to be emulated. [**PouchDB**][pouchdb] is another great example: it's a full reimplementation of [CouchDB][couchdb] that targets JavaScript environments, mainly the browser and -Node.js. However I want a tool that can be deployed anywhere, and not limit it's +Node.js. However I want a tool that can be deployed anywhere, and not limit its applications to places that already have a JavaScript runtime environment, or force the developer to bundle a JavaScript runtime environment with their application. This is true for GTK+ applications, command line programs, Android @@ -72,7 +72,7 @@ apps, etc. [pouchdb]: https://pouchdb.com/ [couchdb]: https://couchdb.apache.org/ -[**Mentat**][mentat] was an interesting project, but it's reliance on SQLite +[**Mentat**][mentat] was an interesting project, but its reliance on SQLite makes it inherit most of the downsides (and benefits too) of SQLite itself. [mentat]: https://github.com/mozilla/mentat @@ -80,7 +80,7 @@ makes it inherit most of the downsides (and benefits too) of SQLite itself. Having such a requirement imposes a different approach to storage: we have to decouple the knowledge about the intricacies of storage from the usage of storage itself, so that a module (say query processing) can access storage -through an API without needing to know about it's implementation. This allows +through an API without needing to know about its implementation. This allows the database to target a POSIX filesystems storage API and an IndexedDB storage API, and make the rest of the code agnostic about storage. PouchDB has such mechanism (called [adapters][pouchdb-adapters]) and Datomic has them too (called |