views:

81

answers:

1

I've settled on the Play framework for the rewrite of our intranet portal. Our portal contains a lot of loosely related stuff so I'm looking for advice on if or how to break it into multiple Play applications.

What are the consequences of making it multiple applications? Is single sign-on still possible? How is access control affected? Am I likely to have to duplicate a lot of code/configuration between them? What else should I consider when deciding where to split things apart?

+1  A: 

First of all I would think about modules, because otherwise you must start a lot of applications, which increase memory consumption. Only if your site is heavy loaded, so that you need multiple server, this doesn't matter.

Is single sign-on still possible? I would say, yes. You can store the data in a cookie, but must make sure that other urls can read it.

Am I likely to have to duplicate a lot of code/configuration between them? Well if you use similar databases this would be another drawback compared with modules, but I wouldn't be to worry about this 1 file of configuration. Code which needed in more than one application can be easily shared via jar-files as a library or you use modules for this.

niels
Hadn't really looked at modules because I think of them as being for reusable components, but after reading up on them they look like a good solution. Structured basically as separate apps but get run from within the main one.
bemace