Need advice about which tool to choose?Ask the StackShare community!
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.
We are planning to migrate one of my applications from MSSQL to MySQL. Can someone help me with the version to select?. I have a strong inclination towards MySql 5.7. But, I see there are some standout features added in Mysql 8.0 like JSON_TABLE. Just wanted to know if the newer version has not compromised on its speed while giving out some add on features.
MySQL AB doesn't implement anything in MySQL until they can find a way to do it efficiently and, often, more efficiently than other systems. So although I don't have experience with benchmarking JSON_TABLEs or similar new features, their development philosophy alone suggests that version 8 for the latest features would be a safe jump without sacrificing system performance.
MySQL 8.0 is significantly better than MySQL 5.7. For all InnoDB row operations, you'll see a great performance improvement. Also, the time taken to process transactions is lower in MySQL 8.0. Moreover, there has been an improvement in managing read and read/write workloads.
While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.
MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.
It was very disappointing.
I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.
I was very disappointed.
Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.
I happen to point my asp.net core web application from MSSQL to MySQL due to infrastructure costs associated with the former db. The application also had challenges creating a migration schema of asp.net membership on MySQL.
After a thorough research I figured out how to do it and also made a video and uploaded to youtube. You can check that here https://youtu.be/X4I0DUw6C84
The full source code for the demo template is available on github here http://bit.ly/2LWgacA
Pros of MSSQL
- Easy of use3
Pros of RethinkDB
- Powerful query language48
- Excellent dashboard46
- JSON42
- Distributed database41
- Open source38
- Reactive25
- Atomic updates16
- Joins15
- MVCC concurrency9
- Hadoop-style map/reduce9
- Geospatial support4
- Real-time, open-source, scalable4
- YC Company2
- A NoSQL DB with joins2
- Great Admin UI2
- Changefeeds: no polling needed to get updates2
- Fast, easily scalable, great customer support2
Sign up to add or upvote prosMake informed product decisions
Cons of MSSQL
- License Cost1
- Vendor lock-in1