This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: RDBMS' are slow
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
The first database I was exposed to while working in the USAF was a full text database engine called BRS/Search. And, lo, it was fast. We're talking gigabytes of data, millions of rows - merely a pittance to this engine.
And then I left the military, became a contractor and was exposed to...Oracle. And, lo, it was slow. Horribly, horribly slow when compared to BRS/Search.
I have it on good authority (i.e. a former colleague who worked with me in the USAF, then worked for Oracle for a time) that they tried to replace the database backend, on the very system I worked on, with an Oracle database. I also have it on good authority that despite several Oracle contractors working to optimize the bejesus out of this system, they still couldn't make it acceptable to the end users - too slow.
The last time I worked on that system was six years ago.
Programmers are always waxing rhapsodic about using the right tool for the right job. The problem is, when it comes to databases, I don't think most know what the right tool is, simply because they've never been exposed to any other kind of database beyond an RDBMS.
Previous Topic
