|
|
|
Average Customer Review
Share your thoughts with other customers
|
|
|
The most helpful favourable review
The most helpful critical review
13 of 13 people found the following review helpful:
key book for enterprise patterns
Even if you find enterprise stuff immensely dull, dealing with databases and web pages is a pretty common task, most of the action in software development revolves around it, and who wants to be completely ignorant of the the alphabet soup of various technologies the IT blogs, books and websites are floating in?
So if you must immerse yourself in this area,...
Published on 29 Jul 2006 by Thing with a hook
|
› See more 5 star, 4 star reviews |
 |
16 of 26 people found the following review helpful:
Good for high level summary. Not complete picture though
Don't really like the way book describes a method in one class then a method in another, then switches back to first class after some explanatory text. Would have much preferred to see complete listings, with section headings and explanatory text with same section headings. It's only when you assemble everything together you find there are a lot of missing pieces that are...
Published on 8 Jun 2004
|
› See more 3 star, 2 star, 1 star reviews |
|
|
13 of 13 people found the following review helpful:
key book for enterprise patterns, 29 Jul 2006
Even if you find enterprise stuff immensely dull, dealing with databases and web pages is a pretty common task, most of the action in software development revolves around it, and who wants to be completely ignorant of the the alphabet soup of various technologies the IT blogs, books and websites are floating in?
So if you must immerse yourself in this area, what better than a Martin Fowler book? The code is mainly in Java, with a fairly large smattering of C#. It would probably help if you understood some basics of enterprise development in those languages, e.g. servlets and JDBC for Java.
The patterns in this book cover organising domain logic, database mapping and access, web presentation, concurrency, and the book finishes by covering base patterns, a mixture of lower level abstractions of the sort covered in Fowler's first book Analysis Patterns (e.g. Money) and those that bear a close resemblance to the classic vanilla Gang of Four patterns, with an enterprise twist (e.g. Plugin and Gateway). Nearly all the other patterns refer to these, so I don't know why these didn't appear first. Apart from that though, the book is very well organised. And the opening essay, that discusses the trade offs of every pattern and how they fit together in an application, is immensely helpful.
Wizened enterprisers looking for new material will not find much new here, but surely the point of patterns catalogues are to get down on paper the practices of those same wizened enterprisers, not to strike off in new directions. Therefore, an experienced developer should see this as a way to organise what they already know, and maybe in doing so, reveal some new insights.
A newcomer to enterprise development will definitely get a lot out of this, as the underpinnings to the plethora of modern enterprise applications are laid bare. You're not going to become a Hibernate, Struts or EJB expert from this book, but you should at least have a clue about what problems they're trying to solve.
As usual, Fowler manages to be a model of clarity, while still injecting regular touches of wry humour, quite an achievement given the potentially bone-dry material. If you want to know the basics of enterprise software, start here.
Help other customers find the most helpful reviews
Was this review helpful to you?
 
|
|
|
|
|
|
20 of 21 people found the following review helpful:
A great book to simplify life of application architect, 1 Feb 2003
If you are an experienced application architect/designer ... you'll probably learn very little new from this book. All patterns described here have been mentioned somewhere else, and has been used for many years. What you will get though is a common vocabulary and very precise and wonderfully written explanations what each term exactly means.
So how this book is to simplify my life? For every new/replacement developer on the project, instead of many pages long architecture document, I'm handling a 1 page summary that uses patterns names from Martin's book along with the book itself and it works beautifully :)
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
12 of 13 people found the following review helpful:
The Authoritive Summary on EA, 24 Feb 2004
What I liked about this book is that it actually covers allot - but only the most important bits about it. Everything you would ever want to know about 3-tier architecture is in this book - if you don't already own it and have an interest in the subject, this is the first book to buy.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
10 of 11 people found the following review helpful:
Must have for serious enterprise/web developers, 12 Feb 2004
This book is more pragmatic, and therefore useful, than most of the patterns books I have read. I have been building .NET apps using the patterns I have applied in previous J2EE projects (mainly documented in Core J2EE patterns). However this book builds upon these approaches and has specific advice for both J2EE and .NET systems. I don't think there can be many developers working commerically with either of these technologies who would not find the ideas presented in this book very useful.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
14 of 17 people found the following review helpful:
Another Bookshelf Essential, 13 Feb 2003
Another bookshelf essential by Martin Fowler. It does for enterprise architecture what the GoF book did for software development in general.Anyone with a reasonable level of experience will doubtless recognise some of the patterns in this book, but in the same way that the GoF book allowed us to communicate by adding patterns to the developer's vocabulary, this book will further expand the vocabulary used by developers, designers and architects of multi-layered systems.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
5 of 6 people found the following review helpful:
Useful but J2EE biased, 30 Jul 2006
I'm a .NET developer and, since the book advertises the fact that it covers .NET as well as J2EE I had high hopes. By and large it lived up to them but in some places I think it let itself down.
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.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
2 of 2 people found the following review helpful:
Save time! Pragmatic, simple and effective, 15 Mar 2006
A very well written and pragmatic book about software architectural patterns.For all the different approches, defines clearly the context of the solution, and, in a critical and structured way, shows the differences among then. Is a book about structured and patronized solutions for typical problems in every day life of all programmers. So instead losing precious hours in front of a computer trying to reinvent the wheel, read this book and learn the some of the best practices from some of the best programmers in the world.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
16 of 26 people found the following review helpful:
Good for high level summary. Not complete picture though, 8 Jun 2004
By A Customer
Don't really like the way book describes a method in one class then a method in another, then switches back to first class after some explanatory text. Would have much preferred to see complete listings, with section headings and explanatory text with same section headings. It's only when you assemble everything together you find there are a lot of missing pieces that are never described. I dived right in to O/R Mapping section and found a lot of method calls and classes that were not discussed further making for only half the picture.
Plus I was a bit disillusioned that author now states on his web site he doesn't have time to respond to emails, so I'll think twice before purchasing another of his books.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
1 of 1 people found the following review helpful:
Good survey, but recent development trends burdons, 27 Jul 2007
Good book. Covers a lot of ground and gives a good survey of the field. Time is on its back, however. The use of web frameworks such as Struts or Spring, and the use of ORM tools such as Hibernate or JPA makes much of the book "redundant". Such tools although solving a lot of practical problems, also introduces many new ones. Maybe a new edition of the book should cover such ground.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
Required Reference, 2 Jul 2009
If you are involved in designing robust, maintainable and highly flexible systems then you have to know these patterns. Other books may go further with patterns now (SOA Patterns for example) but this is the first book every aspiring IT designer should read. It's about clarity and a common understanding in what is still an incredibly young industry. If you want a stimulating and rewarding career in IT and to understand what IT architects are talking about half the time then read and digest this book for a start! Highly recommended.
Help other customers find the most helpful reviews
Was this review helpful to you?
|
|
|
|
|
|
|
| |
|
|
| |
Customers who viewed this item also viewed
|
|
| |
|
|
|
Amazon Home
