> For the other points, please give me the download link of this SQL database that can scale without problems (I want an opensource one since I'm a cheap startu

> For the other points, please give me the download link of this SQL database that can scale without problems (I want an opensource one since I'm a cheap startup). He didn't say that there are such systems, but that he expects them in the next years. > so it's important to have numbers about this superior SQL engines to do some math. In the paper he talks about speedups of 1-2 orders of magnitude compared to current OLTP systems. > I can't imagine how an ACID SQL system is without overhead compared to a key-value store, even when the right technology is used for the implementation. If he is right, then there should be no big difference (maybe 10-20%) between a SQL system and a key-value store, assuming that both offer the same ACID guarantees, because most of the complexity lies in the ACID guarantees and not in the data-storage itself. > Well also I don't think at all avoiding SQL is a bad idea, but the author wrote in this article he is going to show how the other NoSQL claim is false (the claim is that SQL sucks at modeling a lot of problems). He's going to do that in the next blog entry.