Yes breaking you monolithic application into smaller apps is a good idea. However there are some consideration that you should give to inter application communications, such as changes created by the admin app may not be known to the customer app.
The first thing you should do is the refactor you model(s) out of the application into a separate framework. And of course all of the EO's. Regardless of one app or two or more, this refactoring in a must! Jrebel is really help in development but is not meant for deployment. At least that's not what I use it for. Paul Sent from my iPad On Mar 18, 2011, at 1:04 AM, Yung-Luen Lan <yungl...@gmail.com> wrote: > Hi, > > I want to split my one large web application into multiple smaller > applications so that each part running separately because: > > 1. Update one application won't affect the other. For example, I want > to deploy the admin backend but don't want to restart the customer > page. > 2. If one JVM crash, the other is still alive. (Although it cost more memory) > > I'm not sure if my reason is solid. Any comment? > If this is the way to go, how to share the data model between these > applications? Use something like terracota? > Does JRebel help on the point 1? > > Regards, > yllan > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com > > This email sent to p...@mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
