MSSQL vs RethinkDB: What are the differences?
Developers describe MSSQL as "It is an enterprise-level database system that is very popular for Windows web servers". It is capable of storing any type of data that you want. It will let you quickly store and retrieve information and multiple web site visitors can use it at one time. On the other hand, RethinkDB is detailed as "JSON. Scales to multiple machines with very little effort. Open source". RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.
MSSQL and RethinkDB can be primarily classified as "Databases" tools.
RethinkDB is an open source tool with 22.5K GitHub stars and 1.75K GitHub forks. Here's a link to RethinkDB's open source repository on GitHub.
According to the StackShare community, RethinkDB has a broader approval, being mentioned in 53 company stacks & 166 developers stacks; compared to MSSQL, which is listed in 20 company stacks and 22 developer stacks.
What is MSSQL?
What is RethinkDB?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose MSSQL?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using MSSQL?
What are the cons of using RethinkDB?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We initially chose RethinkDB because of the schema-less document store features, and better durability resilience/story than MongoDB In the end, it didn't work out quite as we expected: there's plenty of scalability issues, it's near impossible to run analytical workloads and small community makes working with Rethink a challenge. We're in process of migrating all our workloads to PostgreSQL and hopefully, we will be able to decommission our RethinkDB deployment soon.
Investigating Tortoise ORM and GINO ORM...
I need to introduce some async ORM with the current stack: Tornado with asyncio loop, AIOHTTP, with PostgreSQL and MSSQL. This project revolves heavily around realtime and due to the realtime requirements, blocking during database access is not acceptable.
Considering that these ORMs are both young projects, I wondered if anybody had some experience with similar stack and these async ORMs?
High-speed update-aware storage used in our region server infrastructure; provides a good middle layer for storage of rapidly modified information.
Main database, using it in multiple datacenters in an active-active configuration.