Hello, I have been evaluating OJB for use in our next application and have a couple questions that I hope someone can answer. I've already read through the archives (at least those that matched my query) and saw some disappointing news. However, I want to see if there may be a way around it.
Basically we have a very large database and run a large number of online transactions against it. In the next version, we plan to 'roll-our-own' DB clustering for scalability reasons. We like to be able to partition user records across multiple DB instances based upon a hashing algorithm. The effect of which is to make a transparent layer to store data adhering to a common schema on different physical databases. The business logic would be totally unaware that it's going to different places to get it's data. If I write my own ConnectionFactory this would be pretty easy to do, however I'd really like to be able to use OJB so that we don't waste weeks of time writing O/R classes by hand. From what I can tell, OJB doesn't really support what I want to do.. worse, it appears (from the list archives) that even the described client/server functionality doesn't work. Since this is a production system with paying customers, should I abandon OJB and go for another solution? Thanks, Ryan Clifton Systems Engineering Manager
