Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

10
  • 1
    This is not the most common case for NoSQL. The most common case is availability e.g. the database should always be available, that means that you need a distributed multi-master database. And that is something that traditional RDBMS's is not very good on at the moment. Commented Sep 19, 2011 at 9:41
  • 6
    a relational DB is not good at being available? I don't even know what that is supposed to mean ... Commented Sep 19, 2011 at 10:03
  • Exactly, a traditional relational database is mostly not as available as a NoSQL system. This is the reason why Google and Amazon started to develop their own NoSQL systems. Their business is so important so downtime is not acceptable. Commented Sep 19, 2011 at 10:05
  • 1
    No, that is a different thing. A database can be scalable, but still not have high availability. Commented Sep 19, 2011 at 10:13
  • 3
    scaling is referring to the requests as well. A small database with only 1 recorde on one server is not scaled when you have to expect that a thousand people request that record every second. You are hiding behind buzz-words and you made it your mission to just contradict on this site. Bye Commented Sep 19, 2011 at 10:22