Patterns of Enterprise Application Architecture 1st Edition

It is a great book with many used patterns on a lot of frameworks and libraries nowadays. Also a negative point is some of those patterns are outdated.

The patterns in this book are as relevant today as they were when Fowler wrote them out 14 years ago. You'll find these patterns used in most of the popular (regardless of language) web development frameworks use today. I've owned this book for 7 years and I reference it often as I plan and build enterprise architecture. I came here specifically to write a review after pulling the book down to plan out a new application. To use a cliche, it has stood the test of time.I read in a review that this book is biased toward java: I must disagree--while most of the example are in java (chosen because its a language most developer, at least, know how to read, if not program in), the concepts are universal and can be applied to almost any object oriented language. I've never programmed an enterprise application in Java--yet, it is my go to book when designing architecture for my language of choice.So if you are thinking are buying this and think it is dated: Its not.Or think its for java devs: its not.There's my two cents

I found this book really complete about the issues an enterprise application may encounter. It describes problems and solutions very clearly. The only thing I regret is not to find creation-oriented patterns that may also be usefull in enterprise architecture management. (such as Singleton, Abstract Factory and so on).You'll need some development-oriented vocabulary if you're not used to reading such books, but it's quite well written for people that doesn't read and understand english fluently.

MotivationI didn't look at this book for a long time simply because of the word "enterprise." I felt the word was too overloaded to be useful. I've heard too many managers, recruiters, and other programmers use this word to mean too many different things. Fowler defines enterprise application as "the display, manipulation, and storage of large amounts of often complex data and the support or automation of business process with that data." By that definition every system I've ever worked on has been an enterprise application.ConsA dense, tough read. I almost wish I was at a whiteboard or kept a notepad while reading.ProsFowler gives a fantastic presentation of how to design software using databases, distributed components, etc. This is given through good narratives and anecdotes of Fowler's own experiences, and also through the patterns distilled from these.The best thing I can say about this book is I would put it fourth in the list of books-I'd-like-anybody-I'm-working-with-to-have-read, right after to Design Patterns, Refactoring, and Extreme Programming Explained.SummaryAs with most patterns books, not everything in here is an amazing revelation, but the common approach, terminology, and ways of categorizing problems and solutions make it very valuable.Programmers who utilize design patterns and refactoring, and who work on software systems involving distributed components and/or databases should take a look at this book.

Great condition, except that it is a hardcover and I ordered paperback.

I found this book to be a great resource for understanding many of the prominent frameworks like ORM, ESB and MVC work. I don't see myself ever needing to implement these concepts from scratch, instead I will use existing frameworks that have already solved these problems.The benefit of reading this book is understanding what the problem is, why it's a problem and how to solve the problem. With this knowledge it's much easier to utilize frameworks associated with the patterns and concepts.

good quality

Many of them may seem to be old and outdated but the fundamental concepts still apply today with modern technologies, frameworks are always changing but good design practices stays the same, this book provides a good glance of what issues those architectural design patterns came to solve and yet is solving more complex design issues today.