Mr. Ellison, you're the MS of databases. Don't rejoice too much.
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.
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.