Quick Table of Contents
  1. Table of Contents
  2. Preface
  3. Section 1: Application Design Concepts and Principles
  4. Section 2: Common Architectures
  5. Section 3: Integration and Messaging
  6. Section 4: Business Tiers Technologies
  7. Section 5: Web Tier Technologies
  8. Section 6: Applicability of Java EE Technology
  9. Section 7: Patterns
  10. Section 8: Security

Section 2: Common Architectures

Explain the advantages and disadvantages of two-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

Two-tier architecture is a client/server system.

Properties:

Explain the advantages and disadvantages of three-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

Three-tier consists of:

Properties:

Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

A multi-tier system consists of:

Properties:

Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.

Rich clients

Benefits:

Drawbacks:

Browser-based clients

Benefits:

Drawbacks:

Explain appropriate and inappropriate uses for web services in the Java EE platform.

Use when:

Not to use when:

Comments
qxwerqalwxt - 13 April 2012x6zltZ <a href="http://oyzxkntwwebo.com/">oyzxkntwwebo</a>
penozfzub - 13 April 2012cx9WgF , [url=http://fjdbhnambxox.com/]fjdbhnambxox[/url], [link=http://rmxunzfcpxwh.com/]rmxunzfcpxwh[/link], http://biiwummgzset.com/
Jenifer - 12 April 2012Very very nice post! This should be qeruired reading.If I might suggest a possible followup if you're open to suggestions?It's not uncommon to see the phrase over-architecting , but I've yet to see a published definition or example that I can recall. To me it means basically the bullet points, mainly the one on Needless Complexity . I can easily recognize areas of projects I've written in the past that were over-achitected, my main fault being I think to write wrappers for simple operations when the wrapper was never going to be reused anywhere else.On the other hand I've seen programmers sometimes hear that phrase and seem take it as a license to do no design, no abstraction, and no layering. Which I think is a much bigger mistake. If you're going to err, then err on the side of loose coupling as long as you can keep it all cohesive. In my opinion Anyways, enough blabbing. I mainly wanted to congratulate you on a job well done!
Leave a comment


Name:*
Email:
Message:*
Security code:*
(type the code in the text field)