File Size: 3309 KB
Print Length: 289 pages
Publisher: DVT Press; 2 edition (February 4, 2014)
Publication Date: February 4, 2014
Sold by: Digital Services LLC
X-Ray: Not Enabled
Word Wise: Not Enabled
Lending: Not Enabled
Enhanced Typesetting: Not Enabled
Best Sellers Rank: #128,122 Paid in Kindle Store (See Top 100 Paid in Kindle Store) #49 in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Java #166 in Books > Computers & Technology > Programming > Languages & Tools > Java #393 in Books > Computers & Technology > Networking & Cloud Computing > Internet, Groupware, & Telecommunications
How often do you read a book and end up being confused what to do next? Derek is not a "pure theoretical" guy. You don't need to know him to realise that. Once you read the book you come to realise his experience in the Java EE domain and notice valuable pointers.Next, how often do you long to get back to your IT infrastructure to implement what you read? My guess is just a few readings. This book is special because as you read it, you would want to actually do what is told in it. Your fingers keep itching to do some refactoring and add a few new things you learned. Yes, I code. I hate to just design stuff.So who am I? What credibility does this review carry? Right now I work at HP Singapore as a Senior Systems Analyst. I run my own company in Delaware, Adimpression LLC. I do a lot of design and coding (All open sourced here: [...] ).To add to the review a few pointers you might want to follow in Java EE, which I didn't realise them until too late:1. Always remember, distributed transactions come at a cost and don't scale as smoothly as you think2. Stateful session beans don't mean they are "per user". Rather, they mean "per thread". So find a way to hook them up with HttpSession if you are building a web application.3. JSR's are the best place to clarify a theoretical confusion, such as: What happens during a roll back if a TransactionAttributeType.NOT_SUPPORTED is nested inside a REQUIRED? Can you nest a NEVER inside a REQUIRED transaction?4. Favourite Java EE container to consider? TomEE. Very lightweight and all Apache.There you go. Honest review :-) HTH
I would highly recommend this book to technical architects responsible for the design and delivery of moderate to highly complex applications.Too often we throw around the term of technical architect without it meaning anything more than being a really good developer. I believe this book covers the aspects of being a technical architect that too often missing.* Understanding the skill sets needed on a project* Putting together the correct team* Strategies for getting a clear definition and scope for the project* Architectural & design options vs implementation of a product* Designing for maintenance* Testing strategiesIf you are looking for a technical reference book, this is not the book for you. If you are looking for a book that covers what a technical architect needs to know to do their job, this IS your book.
Nice summary and helpful thoughts on best practices. But it is comparatively pricy. That's why I gave 4 stars but not 5 stars.Sometimes, I will take out this book and review some highlights to help me make decision on my projects.For experienced architects, it confirmed and suggested many practices for the real cases. For other types of technical guys, don't buy it. It will be useless, boring and tedious.
Architect's Handbook...a roadmap for business capability development & delivery in Java. Clearly written sections cover the end to end process from working with the business to define the need, designing the solution to fulfill functional requirements, incorporating non-functional considerations in the technical design, best practices for the Java design, and system verification to deliver the desired business capability that is "fit for purpose and use."Cogent and complete, this handbook lives up to the title.
I liked this book a lot. It may not have thrilled the purists, but this book is written from a practical angle so that anyone can carry this with them on their job and actually do things. I agree with some of the things he says like just focus on 3 to 4 design patterns and not get too theoretical in capturing the minutest of details in the design. These are so relevant and true, especially for large projects. I know this because I have managed large, enterprise wide transformation projects and sometimes people tend to overdo this, forgetting the real objective of why they began the design, which is to get developers started and ensure that both the business and development teams are on the same page.
Excellent book, very concisely written and has great information. A book well worth reading: one does not need to [aspire to] be an architect in order to write better software or to notice whenever a discussed design is not very sound.
Very addictive book. First of all I'd like to highlight the target auditory of this book. It's either a junior architect or senior developer. The author's style is very impressive, he does not use uberqualified terms or definitions. The book will structure your knowledge and vision about being an architect. I highly recommend this book even for very qualified persons. This book is also a good jumping-off ground for understanding of your next book. There is one more important benefit. The book is well organized and provide easy way to navigate to particular question.
This is a great book, looking from a sharing experience point of view. I would definitely recommend this reading towards anyone that has the interest or is on your way to become an Java EE Architect. This book is not technical, it concentrates on best practice and common work process that all real architect should be concern about.