Tag: architecture

Fat Clients

Thin Clients

Poor scalability

Poor manageability

Reduced performance

Reduced separation of business logic

This solution has fat clients

This solution has thin clients

There is a good separation of business logic

The solution has good Scalability

There is a poor separation of business logic

The solution has poor scalability

true

false

not sure

none of the above

Code Break up

Code engineering

Code Tiering

Code Factoring

Modularizing Code

Using well defined software design patterns

Using Servlets to manage distributed database access

Using JSP Scriptlets to locate enterprise beans

Using Data Access Objects when Session Beans or BMP Entity beans have to communicate to the database

Create a DMZ between the two networks.

Create a VPN between the two networks.

Create a secure network connection between the two networks by using a combination of Java sockets and JSSE.

This is not possible, as the corporate firewalls would block this.

Provides very good client security, persons without a client cannot access system.

Ability to access the client's PC utilities or Native API's.

Maintainability of application code is good.

UI changes are easily and immediately available to the clients.

Developing the code.

Confidentiality of code

It is very hard to deploy.

Javascript should never be used for Java EE applications. Java EE specification does not mention about javascript.

Implementing a solution with guaranteed message delivery.

When there is a need to exchange data between different applications on different platforms.

Application is a rich-GUI with minimal interactions with database

Applications need to exchange data in an an interoperable way.

JAX-WS talks about Web Services where as JAX-RPC is not related to Web Services.

Both use JAXB for data binding

JAX-WS uses JAXB for data binding.

JAX-RPC uses JAXB for data binding.