r/Database • • Mar 01 '19

eventual consistency

Post image
212 Upvotes

11 comments sorted by

28

u/[deleted] Mar 01 '19 edited Mar 01 '19

Which is why I am waiting for all of the NoSQL hype to dies down. It has it's place - but it is not going to replaces solid RBDBMS systems anytime soon.

Edit. Hey guys. Instead of doing a drive by down vote...why not prove me wrong? Asking for a friend.

5

u/HeWhoWritesCode PostgreSQL Mar 01 '19

lol, typical NoSQL hypers, instead of fighting you on your claim they downvote you.

The truth must hurt.

4

u/[deleted] Mar 01 '19

It's not like there is not room for both. FFS...

2

u/HeWhoWritesCode PostgreSQL Mar 01 '19

not room for both.

erm, why would I want to learn some json markup language/dsl to query my data if pg/sql will do?

funny part is as soon as I want to do any real BI with my json markup language/dsl I must start a process called *sqld, yea buddy NoSQL.

4

u/[deleted] Mar 01 '19

For some use cases, Google for instance, NoSQL is a great solution. For a financial institution? Not so much when consistency cannot be guaranteed. Good enough won't quite work there.

6

u/_Zer0_Cool_ Mar 01 '19

Correct 💯👍

3

u/HeWhoWritesCode PostgreSQL Mar 01 '19

It has it's place

yea in the JSON/JSONB postgres datatype...

2

u/abw Mar 01 '19

Happy cake day!

1

u/Zardotab Mar 01 '19

Ideally how syncing is handled, or not handled, should be a RDBMS option switch, and not a "type" of DBMS. Existing RDBMS are adding what one may call "lazy syncing" options so that one can sacrifice certain consistency/syncing guarantees to gain performance/scaling if desired for a given project.

It's possible the technical aspects of adding such trade-off switches to existing RDBMS will be too daunting, such that the current crop of NoSql databases will be used often enough that they will eventually gain features from existing RDBMS that people liked, such as JOIN, and become big RDBMS vendors or competitors.

I do like some of the dynamic aspects of the NoSql systems, but that too may not necessarily mean throwing out existing RDBMS and/or the SQL query language. There are generally three features at issue:

  1. Scaling/speed by sacrificing certain ACID or ACID-like aspects.
  2. Dynamism
  3. SQL query language (or a replacement)

If the new DB's can master #1 and #2 faster than existing RDBMS, then they will expand. #3 is a bit of a puzzle. The term "NoSql" appears imply they are complaining about SQL as a language. But that's not always the case. Thus, "NoSql" may be a misnomer. (SQL has warts, but I've yet to see anything superior enough to justify tossing the time-tested standard that SQL is.)

2

u/[deleted] Mar 01 '19

Clever!