Mr. Ellison, you're the MS of databases. Don't rejoice too much.

Much to my surprse, last time we had an Oracle sales team in they mentioned that Oracle is now in the business of NoSQL databases in additional to all the other database products they sell.

Isn't that basically Berkeley DB?

No, they make an actual NoSQL database now: http://www.oracle.com/technetwork/database/nosqldb/overview/...

From the data sheet: "Oracle NoSQL Database is built upon the proven Oracle Berkeley DB Java Edition high-availability storage engine". So it's BDBEE…

That is for the data store itself, and doesn't mean that the database is NoSQL or not. MemcacheDB for example is a NoSQL database that uses BerkeleyDB as a datastore. No different than you'd use InnoDB or RethinkDB with MySQL.

Is it significantly different from Riak? They seem very, very similar based on my superficial knowledge.

It blows my mind that something called Berkeley DB is owned by Oracle. You'd think it'd be a UC Berkeley project.

Awww.. you mad... I'm so sick of hearing about all these "new" technologies that are so revolutionary, but can't hold a candle to postgres and memcache.

Despite what the brochures tell you, a "degree" from DeVry and 3 hours in a Ruby book doesn't make an architect, and this is one of several "revolutionary technologies", like Ruby, that won't scale and will wither and die.

Exactly, how does a programming language scale or not-scale? Ruby might be slower and hungrier (memory) than other languages but it's the applications that might or might not-scale.

Assuming you have the most efficient code possible, the efficiency and speed of the interpreter can still affect the ability to scale an app.

Another thought is, the interpreter may or may not have scaling / clustering available, be it through a built-in functionality or an external queue or something.

Sometimes we have to code around interpreter/speed issues. I work in the JVM languages sometimes. I have to do things differently directly in Java if a particular JVM language I use isn't cutting it. Same goes for ".NET", which is over 30 some languages.

Go ahead and write your self-congratulatory blogpost when Ruby "withers and dies". If HN is still around in 40-50 years, I'm sure it'll hit the frontpage.