We’ve talked at a very theoretical level about how J2EE patterns can help simplify complex web applications. We’ve also talked about the software design principles that underlie J2EE patterns. With that foundation in place, let’s get our feet wet by talking about a few of the simpler J2EE patterns. All three of the patterns we’re about to discuss share the goal of making remote model components manageable.
Once upon a time there was a small dot com that had a website that offered home brewing recipes, advice, ingredients and supplies for beer aficionados. Being a small company (with big plans), they had only one production server to support the site, but they had created two separate software development teams to grow the application. The first team, known as the “Web Designers” focused their attentions on the view components of the system. The second team, known as the “Business Team” focused on the controller components (Rachel’s focus), and the model components (Kim’s area).