monolithic application

[JLivermore]

SmartClient Version: SC_SNAPSHOT-2011-01-06/PowerEdition Deployment (built 2011-01-06)

We currently have 3 applications that make up our build/war file that gets deployed. We're using SmartGWT on the front end with a thin Spring layer in the middle and our DB underneath.

Is there any advantage to breaking apart the 3 apps into individual war files from a SmartGWT perspective? We are only using SmartGWT for the front end code and communication back to the middle tier. We are using Spring in the middle tier (not SmartGWT's server product).

By breaking out the applications, we would have to use single sign on mechanism provided by Spring Security to go from app to app.

Would this imply all the SmartGWT javascript libraries would have to be downloaded for each of the 3 application front ends?

[Isomorphic]

What kind of advantage are you looking for?

You seem to have a pretty good handle on the complexity involved.

It is possible to cause all the apps to load the same .js runtime by <inherit>ing the *NoScript SmartGWT modules and having all apps use the same URLs. Doing this can make it more complex to deploy an update to just one of the apps, which is usually one of the primary reasons people think they want to split apps (and very often not an achievable benefit in practice, due to other dependencies like common database tables, SSO, etc).