Blogging Roller

Raible's got a timely find on this first morning of BlogOn 2005, a happy Roller user who writes (and I'm picking the same except that Raible did):

Roller, on the other hand, uses things like Hibernate to abstract away queries from the underlying DB implementations, and Velocity to separate out the display logic from the business logic. And blogging software does have business logic, or a model; blog entries and categories and tags and authentication and the manipulation thereof are not simple. As a result, I see features being added to Roller that I'm surprised to see happening so quickly.

There's a surprising (or perhaps not so surprising) number of PHP programs, intricate ones at that, that have developers who didn't bother to abstract away the database layer, and wrote DB-vendor-dependent queries. That's a pretty horrible thing to do, since it ties you quite firmly down to one DB (in many cases MySQL). The SQL code is often very tightly integrate with the display code; it's bad enough in the business layer, but the view layer as well? Good gods.

Very nice. Architecture is only one of the many reasons you should consider Roller for any large or "enterprise blogging" installation. And it's only one of the reasons that Roller is advancing so quickly; some great developers have joined the team recently (Allen Gilliland and Elias Torres for example) and we've got demanding bloggers at both Sun Microsystems and IBM pushing us along.

Tags: topic:{technorati}[BlogOn], topic:{technorati}[BlogOn2005], topic:{technorati}[Roller Weblogger], topic:{technorati}[Enterprise Blogging], topic:{technorati}[Sun Microsystems], topic:{technorati}[IBM]