3 ms·
If anyone is considering doing something similar today, I'd suggest to take a look at the recent FoundationDB Document layer which speaks MongoDB v3 (https://fo
by alexandre_m 8y ago
If anyone is considering doing something similar today, I'd suggest to take a look at the recent FoundationDB Document layer which speaks MongoDB v3 (https://foundationdb.github.io/fdb-document-layer/ https://foundationdb.github.io/fdb-document-layer/).
I haven't tried it yet, and there are some limitations at the moment, but I find it extremely promising.
- grumpydba 8y agoI would advise not to use such a baroque technology unless IT is your main activity. Most of the times a boring database is a better fit. Not everybody can be an early adopter, especially on the software which stores what is arguably your most precious asset.
- alexandre_m 8y agoI agree with the boring database, it's most often the good choice. Elaborating on my comment though, it would make sense to consider a drop-in replacement for a technology for which you've already invested yourself, but got bitten enough time to think about moving away to a different model (operational burden, data loss, etc). I'm not sure if "baroque" is a good qualifier for FDB. It's recent in the open source community, but has been running in production for many companies (including Apple) for some years. It's based on sound architecture, compare to many others.