Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part 2 - clustered deployment hor high availability

 
Claudiu Dumitrescu
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

For the part 2 I'm contemplating the possibility of a clustered ear deployment in order to assure a high availability. So it will be something like one web server and one application server with two (or possibly more) partitions.

- I think in this case I'll be forced to introduce the Service Locator at the web server level. What do you think?

- Does anyone know how should I go about the JMS Queues? How should I address the replication for these? It is a service usually assured by the application servers?

Thanks,
Claudiu
 
Arnold Reuser
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A few issues related ot high availability :
* What if your web server crashes for some reason?
* What if the server of your webserver crashes?
* What if a whole datacenter goes down?
* ...

Have a look at the book GlassFish Server Open Source Edition 3.1 High Availability Administration Guide
Issues related to load balancing, clustering and failover of web - and application servers, messaging systems, ... are all described in detail.
 
Rishi Shehrawat
Ranch Hand
Posts: 218
Hibernate Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You need to consider serialization overhead due to split. Also the added complexity in deployment & additional servers due to the split. It is possible to achieve availability by keeping the web & business tier together. You just need to ensure that there is no single point of failure.

For JMS queues you should look at clustered JMS set-up.
 
Claudiu Dumitrescu
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, perhaps it better to keep them together. As a bonus I'll simplify the security issue as well.

Did anyone felt like using a JMS standalone server as part of deployment plan? Are any obvious detriments?

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic