AllSQL

NoSQL is best for WebScale Applications where you fetch data a lot and don’t mind in showing stale data to users. NoSQL cannot guarantee durability of transaction. NoSQL cannot be used in Applications where you want always consistent data meaning latest committed record always at any cost.

If your requirement is Transaction with 100% confirmation (either it happened or not) NoSQL will make you go crazy and somehow if you try to implement it in NoSQL you will realize it to be futile exercise because to make consistent view from the time transaction started , take locks on db objects etc. wont’t happen as desired or not supported at all.

You cannot have Transaction with commit, savepoint, rollback etc. also nested/autonomous transactions are out of question in NoSQL.

SO NoSQL cannot replace relational database at-least next 5 years or so…

NoSQL plays well with storage & querying of BigData in which data is normally written once and read millions of times daily.

I’m sure research must be on going to make new database which is both

NoSQL + SQL = AllSQL

So let’ hope to see AllSQL in future until then use SQL & NoSQL based on pure requirements and business logic.

AllSQL is union of ACID + BASE

1) Distributed Computing and Scaling

2) Support Transaction & Nested Transactions

3) Horizontal Scaling/Resources at its best

4) 100% Available in theory ( 99.999 percentile practically)

5) Low Cost

6) Latency & Throughput meets expectation

7) Code should reach data to reduce network I/O

8) Always user gets consistent and last committed record.

9) Support lock on db objects if needed

It’s not easy to make above but human brain know no limit and humans are best in doing unthinkable inventions.

Any Guess when AllSQL will be out in market ??