Most web apps will never reach the level of scale that cannot be handled by a well coded app with well managed centralized atomic data stores (RDBs being the mo

Most web apps will never reach the level of scale that cannot be handled by a well coded app with well managed centralized atomic data stores (RDBs being the most prevalent). If you are building something with tons of content (video, images, pages that rarely change) you won't store this in an RBD, but your other data can certainly be managed well with one. I've seen lots of poorly written apps which in turn have severe RDB bottlenecks. But this doesn't mean the RDB itself needs to go away. It you need atomic commits (and most apps do for some aspects of the app), an RDB is a good choice. Besides, Oracle isn't even on the radar of most web apps; which go with MySQL or PostgreSQL. This article is mostly gibberish.