>> 3) Is the Derby PM considered production worthy? Any reason not to use it? > Personal I trust derby as a low overhead database with zero > administration. It's not suitable if you have strong dba person which > she/he may lose job:) You may use other db if: > * Prepared to manage database. > * Multi connection required (embedded db using single connection always) > * Cluster your db > * Huge db size > * You application will use exist db along with jackrabbit >
What do you mean that the embedded db can only have a single connection? If I run my repository in some server fashion, such as RMI or SPI, can I still connect to the repository from two applications at the same time? Or is this the type of multi-connection you are talking about.
