3 ms·
@Slava and others. When it comes to database, you know, there is always a fear... A new company, young (extremely talented though) folks, etc. You need to put
by tzury 13y ago
@Slava and others. When it comes to database, you know, there is always a fear... A new company, young (extremely talented though) folks, etc.
You need to put out in the front page of your website use cases. Real world use cases where one can read testimonials and facts, regarding RethinkDB capability, readability and stability.
It will help people to make the step toward trying it, and if they'll try, and get satisfaction, they can end up using it in production.
- qznc 13y agoThere is a prominent note on the website: "RethinkDB is a new system and is likely to have quirks." I applaud their honesty.
- orthecreedence 13y agoI think Rethink is general enough that they don't need use-cases listed on the site. It's not an in-memory database geared towards real-time analytics, it's not a clustered map-reduce system for number crunching, it's a document-based database with real durability and a great query language. Use your imagination. You're right though about the fear of putting your company's data into a new system. However, I think they've taken the right approach by warning people of the risks while at the same time working as hard as they can to mitigate any of the risks. Getting people to trust you is a slow but steady process, and I think they're playing it right.