Pearsonn 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.

Motivation I 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. Cons A dense, tough read. I almost wish I was at a whiteboard or kept a notepad while reading. Pros Fowler 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. Summary As 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.

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.

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 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.

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

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.

iyi ürün

En este libro se encuentra una colección de patrones o soluciones que se han usado, se usan y se usarán en las aplicaciones empresariales, o sea, aquellas comúnmente llamadas "gestión comercial" o "gestión empresarial" y que ahora tienen nombres impronunciables formados por interminables siglas. La mayoría de este material está en Internet y es conocido por cualquier programador con experiencia en aplicaciones de gestión. Pero sorprendentemente aquí, en estas páginas, está todo estructurado y condensado de un modo magistral. El libro está dividido en dos partes: un tutorial extraordinariamente asequible y ameno, incluso con buen sentido del humor, y un catálogo bien pensado y bien desarrollado. La redacción es excelente y accesible (especialmente para Hispanohablantes). Desde aprender hasta confirmar, refrescar o contrastar lo que ya se sabe, cualquier programador, analista o estudiante debería comprar y leer este libro. Los ejemplos están escritos en Java y C#, aunque no hay código fuente disponible pues no es necesario; el código solo se necesita para mostrar algún concepto, no para su ejecución.

Es un libro que incluye diversos patrones que se usan en el día a día en diversas herramientas de la industria. Por ejemplo, el patrón DTO, el patrón Lazy Load, el patrón Repository, etc. El libro llegó en buen estado, dentro de una bolsa. Las hojas no son tan delgadas cómo en otro comentario leí, pero tampoco son tan gruesas como en otros libros, más bien parecen hojas de periódico, ligeramente más gruesas. Lo que más me gustó es que el índice de cada patrón viene marcado cómo si fuera un directorio telefónico como los de antes. Una chulada de libro.

I consider this one as a basic reference on my bookshelf. While I found GoF very useful as one of this books that make you think and show you the way to your programmer's career when you are not very experienced, Fowler's book adds the enterprise touch in a way I enjoy each time I get back to the book. I tells you about those many things in real life applications that you may have not come across yet and you need to develop carefully when you are working in a big project. The enterprise approach to patterns is light but described in a rigorous manner. I must confess I enjoy these books that are not tied to a given version of a given language much more than the rest. The information you get is more open and you get a better understanding of the big picture. If this one doesn't become a timeless reference (the way our profession changes I wouldn't dare to say so from any book), it will sure stand as a classic of its era.

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.