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: 答复: Derby for multi-tenancy environment
Date Thu, 08 Feb 2007 16:29:36 GMT
Yifan Wang wrote:
> 	Generally, Multi-tenancy means "many customers reside on one
> database".
> They can share the same database instance or even share the same table.

Hi Yifan, thanks for sending the links on Multi-Tenant architecture.

>From what I read, Derby is an excellent candidate for this type
of usage:
 - the Derby engine can support multiple databases simultaneously,
   so if you want to place each tenant in its own DB, no problem.
 - the Derby engine fully supports schemas, so if you want to
   place each tenant in its own schema, no problem
 - you can include a tenant id in each table, if you choose that
   design, should be no problem
 - you can dynamically alter table definitions, so as tenants
   choose different features, you can change the table definition.
   Some ALTER TABLE features were present in 10.1, more were added
   in 10.2, and more still have been added to the trunk.

Overall, it seems that Derby would be a fine choice.

Please let us know your experiences with Derby in this area.



View raw message