Episode 1 - Mongo DB Is Web Scale

Q&A discussion discussing the merits of No SQL and relational databases.

• Category

  Comedy

[supergenius1994]

"you are going to blow some project to hell, because you get a woody playing with software like it is a sex doll"

unzip ; strip ; touch ; grep ; > finger ; mount ; fsck ; > more ; yes ; umount ; sleep,

well it seems Linux is a sex doll

[user696969]

love how this is the first result for mongodb search, lol

[cosmicnag]

lol...its fukin funny...though misleading.. i use both mysql and mongodb for the same project... one has to know where to use what... but hats off for the humour...

[srki22]

That means that if something happens to connection or ATM your balance will be reduced and you will not get your money and you will need to go to bank and complain. There are other problems with bank transactions happening all the time. Search for "your atm doesnt use transactions".

[srki22]

If it is scheduled for later that means that it is not ACID. You are right that SWIFT sessions are ACID but it not the same. For scheduled transactions you don't need Oracle.

Also when you withdraw money from 2 different ATM in the same time many banks will just process your transactions in parallel and your balance will be negative if ATMs are geographically distant.

Also if there is no money in ATM many banks can't rollback and instead make a reverse transaction. That is not ACID.

[codesharkc]

LMFAO

[ElderSnake90]

"Mongo DB handles web scale. You turn it on and it scales right up"

LMAO

[Meyer Mack]

Haha yes, /dev/null would be the perfect data store for 99% of the web. It doesn't get more "web scale" than that! And it's FAST!

For everything else, there's Caché.

[Peter Shaw]

@crubixmeister & @srki22 - actually your BOTH wrong. It depends entirely on the product, the company that developed it AND the bank that runs it.

Some will / do ensure that all transactions are AcID compliant, some don't.

And please let's NOT FORGET, in most cases it's not the individual banks that do the clearing, they most often just act as message brokers. The clearing is generally don'e by one of the larger upstream clearing houses that consolidate all the requests.

[cubixmeister]

You're very, very wrong. Bank transactions are ACID. When you 'perform' transfer in web interface or go to the bank it is only scheduled and receiver account is not fully verified. Real account information is exchanged during SWIFT sessions, and they're fully ACID. Balances are always consistent.

[srki22]

Do you realize that bank transactions are not acid, they are eventual consistency. If I transfer $10 to your account you will not see that money until tomorrow. Are balances are not consistent for a day. There is nothing wrong in using NoSql for bank transactions but not every nosql solution is good for that kind of transactions.

[garouHH]

To add a little bit of actual info (state: December 2012), do not use MongoDB if:

1) your application is write-heavy (MongoDB uses one write-lock per DB and daemon)

2) you need complex transactions and can't move all relevant data into single documents

3) MongoDBs (rather rich) query syntax doesn't satisfy your needs

4) you can't figure out good shard keys

5) you need true data locality (MongoDBs mapreduce is a single-threaded sham)

Other than that, I love MongoDB, performance- and syntax-wise.