Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:EclipseLink/DesignDocs/328937
First, let me appreciate James for coming up with this excellent Project Idea. This will make eclipselink the ideal persistence solution for any application that needs to scale; Adding Replication to the list of supported features makes this project all the more useful for enterprises. Today, companies have to rely on several different tools one for persistence, one for caching, one for replication, one for scaling, etc. When this project is completed, eclipselink will become the one-stop solution for accessing databases for any java based applications.
Now there seems to be collision in the efforts needed for accomplishing the two concepts:
1) Database Partitioning (EclipseLink/DesignDocs/328937) and
2) JPA Support for Session Broker (EclipseLink/DesignDocs/328404).
Shouldn't they both be brought under one umbrella? Otherwise, the JPA Support API for session broker may need to be altered again to support the partitioning features. It would be better to to track the development of these two subsystems of eclipselink on the same wiki page.