java - Applications sharing common domain objects from database -


first, background. @ work, have many applications share similar (or exact overlap of) domain objects regards business area of our company. have standardized on eclipselink our orm solution , have domain project holds these data concepts. when data needed, trivial grab domain project's jar , add needed classnames new app's persistence.xml file.

this works great code re-use perspective, however, since happening across disparate apps, caching happening locally inside apps, not across them. i've looked eclipselink's cache coordination, seems more interested in caching 1 app's data across cluster. instead, i'm thinking writing app fetch domain objects database , serve them via webservice of other apps need said data.

my question is, appropriate architecture caching objects database, or going wrong?

well, basically, you'd creating app should handle database access , caching (to avoid going database time).
fine architectural pattern, aware each app should no longer "trivially grab domain project's jar"; you're gonna need define how apps access central data access , caching app.
think you're going in challenges that, i'll happy read comments , other answers.


Comments

Popular posts from this blog

apache - Remove .php and add trailing slash in url using htaccess not loading css -

javascript - jQuery show full size image on click -