Hi Patrick,
in general there is no problem with your idea to run castor as an remote application and it is also possible to co-locate this app. on a database server. Quite some of castors users, including myself, are using castor in this way for a small to medium number of users. But if the number of users increases, the load on this single maschine also increases and you will reach a point where you need to think about solutions to reduce the load on that single maschine. As a frist step you can run your castor app. and the database on seperate maschines. If your castor app. server is still overloaded you can run your castor app. on multiple servers loading data from one database server. Only in this case you will need to synchronize the cache of all castor app. servers.
Using multiple replicated database servers with a co-located castor app. is not a solution to that problem as you need to switch of castors cache if records on the database server are modified by any other app. including the database server itself. That's exactly what happens when replicating databases. Having said that when you switch of castors cache you will recognize a dramatic loss in performance.
Ralf
Patrick Finnegan schrieb:
Would it be possible to turn Castor into an application running in a JVM providing JDO services to remote java applications? The "Castor App" could be co-located on a database server thus avoiding the distributed cache issue.
