CODE [sic]

Contributing to the web technology conversation

Skip to content
  • Home
  • About
  • Why you should be using an Object Database instead of ORM: Part 1

    01-08-2009 7:03 AM

    I think traditional relational databases (RDBMS) are generally crappy for as the data store for complex dynamic web sites.  But despite the inflammatory nature of that first sentence, I'm going to try not to turn this into a rant.  Instead, I'll try to explain the problems I see and why I came to that conclusion.

    The problem with RDBMS

    First of all, I don't have a problem with RDBMS.  I think it has served us very well up to this point and will continue to do so for the forseeable future.  It's a perfectly workable solution to the problem of storing and retrieving persistent data.

    Keep Reading Why you should be using an Object Database instead of ORM: Part 1 ยป

    comments (7)

I like open software

Calendar About Nothing tracks my public contributions on GitHub.

  • Categories

    description
    List of Categories for Posts
    • axiom stack (2)
    • blog updates (2)
    • browsers (1)
    • content management (2)
    • databases (1)
    • e4x (1)
    • exception handling (1)
    • extjs (1)
    • facebook (2)
    • firefox (2)
    • firefox add-ons (2)
    • google chrome (1)
    • greasemonkey (2)
    • imho (3)
    • java (1)
    • javascript (4)
    • libxmljs (1)
    • markdown (1)
    • narwhal (1)
    • node.js (2)
    • OODB (1)
    • opinions (1)
    • RDBMS (1)
    • safari (1)
    • semantic markup (1)
    • serverjs (1)
    • stupid dev questions (2)
    • uneducated opinions (1)
    • wysiwyg (1)
  • Recent Entries

    title
    Recent Posts
    description
    Most Recent Posts by Date Published
    • A quick rant on web development and elegant solutions
    • The Node.js Community Could Use Some TLC
    • A quick project to create an ebook from html
    • Updating libxmljs on node.js: or, how to suck less at Google v8
    • Creating a Blog I'll Actually Use

Powered by Axiom® Stack