Over the last few years, Java 2 Platform, Enterprise Edition (J2EE) technology has emerged and matured as a standard platform for building enterprise applications. While the platform has matured into a solid offering for developing and deploying enterprise applications, it does offer its challenges.
J2EE Design Patterns
โ Scribed by William Crawford, Jonathan Kaplan
- Book ID
- 127433978
- Publisher
- O'Reilly Media
- Year
- 2003
- Tongue
- English
- Weight
- 1 MB
- Edition
- 1
- Category
- Library
- ISBN
- 0596004273
No coin nor oath required. For personal study only.
โฆ Synopsis
Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes. It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns. A software design pattern can be identified as "a recurring solution to a recurring problem. Using design patterns for software development makes sense in the same way that architectural design patterns make sense - if it works well in one place, why not use it in another? But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started. Crawford and Kaplan's J2EE Design Patterns approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software. They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability. J2EE Design Patterns offers extensive coverage of the five problem areas enterprise developers face: * Maintenance (Extensibility) * Performance (System Scalability) * Data Modeling (Business Object Modeling) * Transactions (process Modeling) * Messaging (Interoperability)And with its careful balance between theory and practice, J2EE Design Patterns will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience.
๐ SIMILAR VOLUMES
This guide presents the best practices for development using J2EE technologies and details 21 design patterns that produce applications notable for their performance, scalability, and robustness. A multi- tier case study illustrates every stage of enterprise development, and sample code is provided.
Developers often confuse learning the technology with learning to design with the technology. In this book, senior architects from the Sun Java Center share their cumulative design experience on Java 2 Platform, Enterprise Edition (J2EE) technology.The primary focus of the book is on patterns, best
There are a number of best practices you need to consider to build highly effective J2EE components and integrate them into applications. These practices include evaluating and selecting the right set of software components and services to handle the job.In this book, Darren Broemmer supplies you wi
As part of the highly regarded Java BluePrints program, Designing Enterprise Applications with the J2EET Platform, Second Edition, describes the key architectural and design issues in applications supported by the J2EET platform and offers practical guidelines for both architects and developers. It
Intended for experienced J2EE developers, this book documents bad practices in the form of antipatterns. Each antipattern summarizes background information on the technology, identifies the symptoms and consequences of the problem, and provides a code example. The second half of each chapter offers