High availability with Glassfsh, some open questions
I am currently working with Glassfish, with a single domain. (1 application)
After few outages on my application, I started to look at installing several glassfish instances and put load balancing there (with apache and mod_jk).
I followed the oracle tutorial, and the load balancing is working well so far.
My questions, so far:
- Apache: How to avoid single point of failure ?
- Is clustering the only possibility to set-up load balancing?
- If I'm not mistaking, there is only one domain, administrating and managing the several instances, right? What happens if the node where the domain is running crashes? Everything is down? How to avoid that? Passive domains on the other nodes?
- Is there other point to consolidate?
I am quite new in the glassfish world, and totally new with high availability challenges.
Please do not hesitate to share comments with me, podcasts, documents, good practices to have a highly available architecture.
Thank you in advance !