https://luminoussheep.net/mediawiki/index.php?action=history&feed=atom&title=Java_EE_Modular_SolutionsJava EE Modular Solutions - Revision history2026-04-16T19:02:26ZRevision history for this page on the wikiMediaWiki 1.43.8https://luminoussheep.net/mediawiki/index.php?title=Java_EE_Modular_Solutions&diff=66&oldid=prevMartin: Created page with "Web tier access EIS direct or though EJB = use of tiers = == Decide on requirements == Based on: * functionality * complexity * scalability == EJB tier == * security * tran..."2021-09-14T21:32:27Z<p>Created page with "Web tier access EIS direct or though EJB = use of tiers = == Decide on requirements == Based on: * functionality * complexity * scalability == EJB tier == * security * tran..."</p>
<p><b>New page</b></p><div>Web tier access EIS direct or though EJB<br />
= use of tiers =<br />
<br />
== Decide on requirements ==<br />
Based on:<br />
* functionality<br />
* complexity<br />
* scalability<br />
<br />
== EJB tier ==<br />
* security<br />
* transactions<br />
* distributed processing<br />
<br />
== Web tier use of JDBC implications ==<br />
* ideal for small simple applications with few transaction requirements<br />
<br />
* implements all core functionality<br />
* implements transaction management - JTA<br />
Implies:<br />
* poor scaling with complexity<br />
* monolithic<br />
<br />
== Using Web and EJB tier ==<br />
* better for:<br />
** building large scale complex applications<br />
** complex security/transaction requirements<br />
** performance requirements<br />
* implications<br />
** Splits business logic into EJB tier<br />
** web tier becomes mainly request processing and view<br />
<br />
= Use of distribution =<br />
Must be designed for distributed architecture <br />
Use of:<br />
* service locator - to hide location/naming resolution<br />
* business delegate - to hide remote nature<br />
* composite entity/transfer object assembler - to reduce fine grained access<br />
<br />
== Local == <br />
* same virtual machine<br />
* no network overhead<br />
* no serialisation overhead<br />
* low latency<br />
* allows for fine grained control/access<br />
<br />
== Remote ==<br />
* more modular<br />
* more reusable<br />
* lower dependency between components<br />
* higher overheads - data copying, latency<br />
* security considerations<br />
* typically more scalable (horizontally) - can split and run on more machines<br />
* more highly available - easier to migrate to different machine in the event of failures</div>Martin