- Capa dura: 560 páginas
- Editora: Addison-Wesley Professional; Edição: 1 (15 de novembro de 2002)
- Idioma: Inglês
- ISBN-10: 0321127420
- ISBN-13: 978-0321127426
- Dimensões do produto: 19,4 x 3,6 x 24 cm
- Peso de envio: 1,1 Kg
- Avaliações dos clientes: 157 classificações de cliente
- Lista de mais vendidos da Amazon: Nº 73,912 em Livros (Conheça o Top 100 na categoria Livros)
Patterns of Enterprise Application Architecture (Inglês) Capa dura – 15 Novembro 2002
|Novo a partir de||Usado a partir de|
Leia Enquanto Enviamos
Compre e comece a ler a amostra digital deste livro enquanto espera ele chegar. Saiba mais aqui.
Frequentemente comprados juntos
Clientes que visualizaram este item também visualizaram
Detalhes do produto
Descrição do produto
The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned.
Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform.
This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts.
Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them.
The topics covered include:
Sobre o Autor
Martin Fowler is an independent consultant who has applied objects to pressing business problems for more than a decade. He has consulted on systems in fields such as health care, financial trading, and corporate finance. His clients include Chrysler, Citibank, UK National Health Service, Andersen Consulting, and Netscape Communications. In addition, Fowler is a regular speaker on objects, the Unified Modeling Language, and patterns.
Clientes que compraram este item também compraram
Avaliação de clientes
Ocorreu um problema para filtrar as avaliações agora. Tente novamente mais tarde.
Principais avaliações internacionais
While there are a lot of patterns here that can be found among those proposed by the Gang of Four or found at Sun's BluePrints website, the explanations of the significance of the pattern and when and where it should be used makes it invaluable to programmers. The patterns covered are almost perfect in that they cover the most commonly used patterns as well as the patterns that can make the biggest difference. It's not perfect though as there are a couple of patterns that you feel were included to make up the numbers ('Money' being the most obvious offender).
Incidentally, it's also a great source for disambiguation of terms too where disparate teams can use terms from this book as a common reference. Very useful when dealing with remote teams.
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 must read of developers working with patterns.
In particular the majority of the code is in Java. I don't mind mentally mapping from Java to C#, however its the differences between the framework libraries that creates the problem as I simply cannot do that mapping.
Despite this the book is OK, if you concentrate on the patterns themselves then your fine but I think Java developers will get far more from it as they're going to learn not just the patterns but details you need to be aware of when applying them.
Die Beschreibungen sind ausführlich, detailiert und sehr gut gegliedert ("How it works", "When to use it", etc.), die Klassen-Diagramme sind groß, übersichtlich, intuitiv und fördern das schnelle Verständnis der Patterns ungemein. Die Code-Beispiele sind ebenfalls sehr gut.
Wie der Klassiker Design Patterns. Elements of Reusable Object-Oriented Software. ("GOF") versteht sich PofEAA als Sammlung bewährter Patterns, und ist damit sicherlich eher ein Nachschlagewerk als ein Buch, das man von vorne bis hinten "durcharbeitet". Es reicht sicherlich aus, sich einen (groben) Überblick über die Patterns zu verschaffen, und das Buch dann griffberreit am Arbeitsplatz liegen zu haben, um dort schnell nachschlagen zu können.
Und genau das geht außerordentlich gut: Genau wie das GOF-Buch hat auch PofEAA auf den ersten beiden Seiten eine Liste aller Patterns mit kurzer Beschreibung und der entsprechenden Seitenzahl. Darüber hinaus gibt es auf den letzten beiden Seiten ein Cheat-Sheet, das direkt auf die richtigen Patterns verweist.
Zu den Patterns als solchen muss nicht viel gesagt werden: "Data Transfer Object", "Model View Cntroller", "Remote Facade" und und und... sind allgegenwärtig - wer sie (und alle anderen in PofEAA präsentierten) verstehen will sollte zu diesem Buch greifen!
A large portion of the patterns covered in the book concern about Object Relational Mapping. I can imagine ORM was a relatively new and challenging topic in early 2000's. Today, with matured enterprise middleware and frameworks, ORM is largely a solved problem.
In the area of distributed computing or "remoting" as the book called it, the advice given by the book is "not to do it". There is very little discussion about Web Services. Needless to say, there is no discussion of cloud computing.
On the bright side, a few patterns (e.g. Data Transfer Objects) in the book does inspire me to look at my previous projects with a new angle.