- 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,3 x 3 x 23,9 cm
- Peso de envio: 1,1 Kg
- Avaliação média: 1 avaliação de cliente
- Lista de mais vendidos da Amazon: no. 89,743 em Livros (Conheça o Top 100 na categoria Livros)
Patterns of Enterprise Application Architecture (Inglês) Capa dura – 11 jul 2016
|Novo a partir de||Usado a partir de|
|Prazo||Valor Mensal (R$)||Total (R$)|
|2x sem juros||R$ 168,87||R$ 337,74|
|3x sem juros||R$ 112,58||R$ 337,74|
|4x sem juros||R$ 84,45||R$ 337,74|
|5x sem juros||R$ 67,58||R$ 337,74|
|6x sem juros||R$ 56,29||R$ 337,74|
|7x sem juros||R$ 48,30||R$ 337,74|
|8x sem juros||R$ 42,27||R$ 337,74|
|9x sem juros||R$ 37,58||R$ 337,74|
|10x sem juros||R$ 33,81||R$ 337,74|
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 compraram este item também compraram
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 visualizaram este item também visualizaram
1 avaliação de cliente
Avalie este produto
Mostrando 1-1 de 1 avaliações
Ocorreu um problema para filtrar as avaliações agora. Tente novamente mais tarde.
Avaliações mais úteis de consumidores na Amazon.com
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