[jboss-dev-forums] [Design of JBoss Portal] - Re: current logged users
Antoine_h
do-not-reply at jboss.com
Mon Jul 16 08:39:17 EDT 2007
Hello,
About JMS or not, it makes me think of architecture, especially in High Availability (working on that now for a big organisation).
You may have yet taken this into account : so, just in case :
An architecture with a producer and some consumers would be great.
Whatsoever is the messaging support between the two.
If not yet : taking this into account in the way to build these services... would be nice.
3 advantages :
1) High availability :
With HA, people need to view/monitor/exploite these material (like statistic and users loged) from another server.
The machine that work with this material will not be inside the HA perimeter.
2) Prod architecture : upgrade of applications
Even with no HA.
The statistic application and the admin application must be upgraded with new versions quite quicly (1 or 2 months),
whereas the portal application will be mainly every 6 months (heavy, high stake migration).
So a separate server for these feature (consumers) is much more confortable (necessary ?) for prod.
3) overriding and extensions
To easily extend the feature : it is more easy not touching the producer, and just override the consumer.
hope it helps...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064518#4064518
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064518
More information about the jboss-dev-forums
mailing list