Is really MySQL ACID compliant?

This is a really interesting question. Many people are force to think that MySQL is not totally ACID compliant due to some limitation of MySQL itself or limits introduced by some particular storage engine.
We cannot hide that old versions of MySQL were not aware of the concept to transaction and transaction is a concept must be present in an ACID database. Also ACID implying a good design of application and data, as said by Alex Popescu:

That’s because you are basically taking your data and vomiting it on the hard drive without any consideration as to if your data you are writing is sensible or simply dreamed up by magic pixies.

You may also find an interesting bug opened to MySQL: bug #62209. There is a nice complain about ACID functionalities when MySQL is used with InnoDB. Jordan Hall also made a simple test about the functionalities of CHECK constraints in MySQL showing that ACID is not totally supported.

At the end, this famous video:

Amazon Gift Card
by: gar1t

The future or no future of NoSQL

Quoting a blog post of the 451 group we can do some remarks on NoSQL. First of all many person do not really know what is NoSQL and the worst of it is that many persons claim to be IT consultant does not really know anything about NoSQL; they simply think that NoSQL is a different kind of database that don't use SQL language!
Second NoSQL is a widespread concept that has been used for different products without really leveraging the single functionalities; this has been caused market confusion and it haven't helped the real diffusion of concept and use.
Probably only few persons known the theory behind NoSQL, the differences between BASE and ACID, te CAP theorem, the differences between NoSQL datastores, etc.
Also today you hear from many sources the term BigData. Do you know that BigData is a trademark of a company called SysTap ?

Furthermore the big problem of NoSQL in the enterprise: is the eventually consistent model applicable to your business?