Choices for Service Architecture

  • Jan Newmarch


A client will only be looking for an implementation of an interface, and the implementation can be done in many different ways, as discussed in this chapter. In the previous chapter we discussed the roles of service proxy and service backend and briefly talked about how different implementations could place different amounts of processing in the proxy or backend. This can lead to situations such as a thin proxy communicating to a fat backend using RMI, or at the other end of the scale, to a fat proxy and a thin backend. The last chapter showed one implementation—a fat proxy with a backend so thin that it did not exist. This chapter fills in some of the other possibilities.


Class Diagram Service Architecture Service Implementation Lookup Service Public Class 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Jan Newmarch 2000

Authors and Affiliations

  • Jan Newmarch

There are no affiliations available

Personalised recommendations