Large scale J2EE options

We're discussing scalability issues with a J2EE system that must support around 40 million entries (one table), each with about 10 entries of related items (other tables).

These entries will need to be accessed quickly and not degrade significantly as the number increases.

The J2EE environment only allows you to specify a single data source for an entity bean. We're looking for a way to do this with container managed persistence to begin with, although I suspect we will have to rethink this.

Based on this we're hoping there's some option at the database level that can provide the performance options we require. I'm thinking in terms of a federated database or something like that. I'm not entirely sure what options Oracle supports in this regard, but I figured that Oracle must scale like this.

My expectation is that we will at least have to use bean managed persistence and manually federate the database based on some criteria. As a very basic example, all entries with names starting with "a" in data source "a-datasource".

What options do we have in the Oracle systems alone that will allow our J2EE system to scale as well?

Any ideas?

Tristan. Received on Wed Apr 24 2002 - 20:32:37 CDT