Hi, I'm thinking of buying Martin Fowler's "Patterns of Enterprise Application Architecture".
From what I can see it seems like a great book, it an architectural book with bias towards enterprise Java -- just what I need.
However, in computer years, it is quite old. 2003 was a long time ago, and things have moved on quite a bit since that time.
So I'm wondering if anyone can tell me: is this book still relevant, and worth the read?
Thanks
I disagree with the "bias towards Java" statement. Patterns, by their nature, are language-agnostic. They're defined as solutions to common problems. The copy of Fowler's book has examples in both Java and C#, so I can't see where the "bias" comes in. They're the most common object-oriented languages, and he's talking about object-oriented solutions to enterprise problems.
The GoF book has examples in Smalltalk and C++. Why are they so "biased" against Java and C#? Hint: the languages didn't exist when that book was written, but the patterns are as relevant as ever.
It's very relevant. I frequently refer other developers to particular patterns from that book, as links to his site (http://www.martinfowler.com/eaaCatalog/), such as Data Transfer Object and Service Layer.
The latter is one I thought I had invented until I saw that Fowler had already written about it.
It's currently the textbook used at my university's Principles of Information Systems Design course.
This book, and Eric Evans book about Domain-Driven Design, are my books of the year - every year ;) ...
Yes the book is still relevant. You can pickup used copies on Amazon if you are worried about its value and sell it through the same channel.
Absolutely!
The book is a classic. I've just been re-reading it to help with some work on event-driven accounting systems.
Fowler has been revisiting some of the patterns since and you can see his works in progress.
Very relevant, and certainly not chained to one language. Witness the upcoming Rails move to Merb, in a very real sense a move from one pattern in POEAA (ActiveRecord) to another (DataMapper).
Many other concepts, from ORM strategies to session management, are both relevant and language-agnostic. I'm still floored when I read this how vast Fowler's influence is. He didn't invent all of the concepts here, but he certainly codified and put names to these ideas in such an concise and accessible way as to make them common parlance across the industry. Still essential.