J2EE Website Architecture

This architecture is for a relatively simple website that uses a J2EE-compliant application server. The diagram shows one new database in the Middle Tier of a website and no existing databases or systems in the EIS Tier. There are four ways that a database could be used in this architecture: 

  1. The first way is with a transparent interface such as Java Data Objects (JDO) coupled with an object database. In this case, there is no need for a mapping layer because the Java object model is the same model used by the object database. See The lack of a mapping layer is show in this diagram.

    J2EE Website Architecture JDO Middle Tier
    J2EE Website Architecture JDO Middle Tier
  2. The second way is with a transparent interface such as Java Data Objects (JDO) coupled with a relational database. In this case, there is a need for a mapping layer because the Java object model may not match the model used by the relational database. Nevertheless, the mapping can be moved to one location as described in Also see
  3. The third way is with a call-level interface such as JDBC coupled with a relational database. In this case, there is a need for a mapping layer because the Java object model may not match the model used by the relational database. The mapping would need to be done at the application level as described in Be sure to take a look at This outlines some disadvantages of using JDBC that you should consider when designing persistence for J2EE.
  4. The fourth way is with SQLJ and a relational database. Having a new database would make it possible to minimize the mapping described in Also see and

Current Article Context

Related Articles

The Savvy Manager's Guide

is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide

by with David Dick

This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.