Modify

Opened 15 years ago

Last modified 9 years ago

#224 new defect

JavaParty as high-performance RMI server in a three tier architecture

Reported by: Chuck Dillon Owned by: hauma
Priority: normal Milestone:
Component: JP environment Version: 1.07h
Severity: normal Keywords:
Cc:

Description

I'm contemplating a three tier architecture. The top/client tier is composed of standard RMI clients built with standard JDK tools running somewhere on the internet. The bottom/compute tier is composed of the JavaParty "remote objects" running on a cluster of Linux boxes behind a firewall. The middle tier is both a standard RMI server to the client tier and a JavaParty front end. So the objects served to the top/client tier are users of "remote" objects. I absolutely do not want these clients to be at the party. The question is whether such a middle tier can be created with the current implementation of JP?

The driver for this query is that we are looking at serving computational bandwidth via the internet. We expect low transaction rates for relatively heavy compute jobs. So, we need to scale well in terms of compute power but have little concern for scaling to support transaction rates. The conventional approach is to adopt an architecture based on an application server (i.e. the e-Enterprise solution) which are really based on the recipricol case. There is a quantum leap of complexity and cost when you go that route, even if you use an opensource application server.

So, I'm investigating the idea of leveraging something like JavaParty to allow us to scale our computational bandwidth without the need for massive amounts of middleware and the headaches that comes with it. As we scale we add machines and grow the party. We can add a lot of Linux boxes at a fraction of the cost of adopting an enterprise middleware solution.

Attachments (0)

Change History (3)

comment:1 Changed 15 years ago by hauma

A proof of concept implementation is described in ThreeTierArchitecture.

comment:2 Changed 15 years ago by hauma

The proof of concept is implemented in [2706] and [2707].

comment:3 Changed 15 years ago by hauma

With [2708] and [2709] the JavaParty transparency layer is used even from within the middle-tier that is not part of the distribted environment.

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain hauma.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from hauma to the specified user. Next status will be 'new'.
The owner will be changed from hauma to anonymous. Next status will be 'assigned'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.