Patterns of Enterprise Application Architecture

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.

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.

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.

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

The Kindle Edition does NOT include any figures or diagrams. Quite an unpleasant surprise when reading passages like "The easiest way to see the difference is to look at the sequence diagrams for the two approaches (Figures 2.1 and 2.2).", clicking on those links and only finding a bare caption with no figure whatsoever. I contacted Amazon's customer service about this, and they replied with a mere "Occasionally, conversion to digital requires modification of content, layout, or format, including the omission of some images and tables". It would be great if Amazon worked together with the publishers to make it clear when there is missing content somewhere in its product page. Paying almost the price of the hardcover to end up with an incomplete product is unfair to say the least, and overall a bad experience for the reader.UPDATE:As of May 3, 2011, the issue with the missing figures/diagrams seems to be fixed.

good quality

Even if you don't do "Enterprise Application" development, this book is a must have in your library. If you have been developing for more than a couple of years and you haven't seen 1/2 of the patterns in this book, then you are probably doing something wrong and this book could greatly help you.Even if you do know 1/2 or more of the patterns in this book it is a great reference to the details of these patterns. Unless you are a Sophomore Software Engineering Student I'd recommend this book over the GoF book. Gof is a must have too, but if you can only have one. Get this one!

I'm sure this book was very helpful for its time, but right now I feel it's a bit dated. Microsoft has moved away from datasets (Thankfully) so some of what it's talking about doesn't make sense anymore. I think the advice is very sound though. Also, internet is a lot faster so I'm not sure if the "Don't distribute your system advice" holds anymore.

Sobre o conteúdo do livro, simplesmente incrível, um pouco obsoledo, mas isso é natural com um tema em constante evolução, todo desenvolvedor precisa ler este livro.Sobre a embalagem, o livro veio solto numa caixa, o que ocasionou algumas marcas do transporte, considerando a aquisição de um livro capa dura (mais caro), quem preparou o pacote já deveria supor que o cliente é exigente, talvez um colecionador.

Excellent book showing a good range of approaches and providing practical advice.

Hood

Me fue muy bien para mejorar en el trabajo

A basic book that helps understanding the foundations of the construction of enterprise systems. It is not the ultimate source of truth though, and requires further reading on the trending topics and concepts that are gaining momentum and have been proven to work.