Hi, I liked your concise description of Slice -- a more verbose description is available at [1].
Slice is designed to handle federation at JPA/application layer and via Slice it is possible to support a multi-tenant environment using a set of databases that are *not* federated by themselves. In fact, Slice can work with the databases that are heterogeneous as well. For Azure or other federated databases, the relevance of Slice is diminished as sharding concerns are handled by database server itself. From a JPA application standpoint, it will see a federated database as a "single" database. So effectively, I see Slice and federated database as an either-or option, depending upon the design decision of which layer (database or JPA) is better suited to handle sharding. However, Slice does provide some extra features such as @Replicated types for master or reference data or query targeting. I would like to know from your experience with federated databases, how these features are supported by Azure. Regards -- ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/Experimenting-with-MS-SQL-Azure-federations-tp7579852p7580058.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
