InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Martin Fowler on Enterprise Rails

Posted by Obie Fernandez on Jul 11, 2006

Sections
Development
Topics
Ruby on Rails ,
Ruby
Tags
Rails ,
Enterprisey ,
rBatis ,
RailsConf
After keynoting RailsConf, Martin Fowler continues to devote attention to the Rails community. In a notable new article entitled EnterpriseRails, he discusses the issues faced by the Rails community with regards to enterprisey concerns. Martin implicitely endorses DHH's refusal to complicate the framework by including things (such as compound primary keys) that go against Rails' opinionated attitudes towards simplicity.
I confess I like this opinionated attitude. Perhaps it reflects my Unix background, which thrives on many tools that do one thing well, rather than a complex tool that tries to do many different things. I like Rails's focus, its determination to pick a certain class of application and serve that well.
Martin then proceeds to praise DHH's ability to break free of the type of constraints presented in enterprise settings.
In this sense I see a startling parallel between DHH and Kent Beck. For either of them, if you present them with a constrained world, they'll look at constraints we take for granted, consider them to be unessential, and create a world without them. I don't have that quality, I tend to try to work within the constraints gradually pushing at them, while they just stick some intellectual dynamite under them and move on. That's why they can create things like Extreme Programming and Rails which really give the industry a jolt.
In the second half of the article, Martin talks about alternatives to Rails for folks who like himself "can't apply the dynamite" by highlighting the work on rBatis being done by our colleagues at ThoughtWorks, led by Jon Tirsen. RBatis was presented at RailsConf by Badri Janakiraman.
rBatis could be the answer to complicated database issues, still fitting into a Rails web-app, but introducing a different set of trade-offs. If you're comfortable with SQL, rBatis looks pretty damn simple.
RBatis would presumably be usable by itself outside of Rails, just as it is possible to do with ActiveRecord.  However, its primary target audience is Rails developers in enterprisey settings. Martin wraps up his commentary expressing hope that that Ruby is not overlooked as an excellent "enterprise glue" because of the opinionated nature of Rails.
Ruby and Enterprise by Alex Popescu Posted
  1. Back to top

    Ruby and Enterprise

    by Alex Popescu

    I've read and listened DHH mentioning and explaining his decissions regarding some parts of Rails. But considering, the enterprise space I am wondering how to put all these together.

    ./alex
    --
    .w( the_mindstorm )p.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.