db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: Stored Prepared Statements? -- Thoughts on exposing StorablePreparedStatements to user/external statements
Date Wed, 15 Apr 2009 20:01:36 GMT
> 1) lock db directory for user (using symlinks -- atomic nfs op) ... would be done external
to derby.
> 2) open database for the user
> 3) do operation to satisfy caller's request
> 4) close db then remove lock.

This seems like kind of a funny architecture. Have you investigated
using Derby's existing client/server support? You could have an
architecture that was more like:
  - each of your N mid-tier apps is a Derby client
  - all connecting to a single Derby server which accesses the
    database stored on the NFS filesystem.

You'd still have the benefit that each mid-tier app could handle
any user request, but you'd avoid the expense of having to open
and close Derby on each request.



View raw message