| ▲ | dullcrisp 38 minutes ago | |
This article doesn’t present much motivation for why you would do this. To me it reads a bit like, how we built our office without desks: it turns out if you stack two chairs on top of each other, you can balance your laptop on the top and you’ll also have a shelf on the bottom for your things. | ||
| ▲ | locknitpicker a few seconds ago | parent [-] | |
> This article doesn’t present much motivation for why you would do this. For those working with databases, it's easy to come up with a bunch of reasons. ORM is a necessary evil when working with RDBMS, as are things like schema migrations that can easily result in loss of data (I.e., dropping columns or tables). What if all we need is dumping a big old JSON in a container? This idea is very enticing. The scale of this whole NoSQL thing is pretty telling. The blog presents a thought provoking question: what if we don't actually need a full-blown database, and instead we only care about things like unique constraints, transactions, indices, and history tables. What if we only need a subset of those? | ||