2 ms·
It's much easier to write in a new database in the future, than it is to deal with greater complexity initially. I find that in the first phases, I often don't
by true_religion 10y ago
It's much easier to write in a new database in the future, than it is to deal with greater complexity initially.
I find that in the first phases, I often don't know what kind of load is going to be where, so I simply use a relational database since they give excelent data security, and okayish performance for most things under low load.
- davidbanham 10y agoI think the inverse is actually the case here. If you need changefeeds, use Rethink up front rather than write your own implementation. When you hit a problem with its performance, then think real hard about your domain and see if it's possible to replicate the safety guarantees it gives you on another DB.