Note that there are some explanatory texts on larger screens.

plurals
  1. PODatabase replication for redundancy using a free database and a Java with Spring & Hibernate web application
    primarykey
    data
    text
    <p>I have this in mind:</p> <p>On <em>each</em> server: (they <em>all</em> are set up <em>identically</em>)</p> <ul> <li>A free database like <a href="http://www.mysql.com/" rel="noreferrer">MySQL</a> or <a href="http://www.postgresql.org/" rel="noreferrer">PostgreSQL</a>.</li> <li><a href="http://tomcat.apache.org/" rel="noreferrer">Tomcat</a> 6.x for hosting Servlet based Java applications</li> <li><a href="http://www.hibernate.org/" rel="noreferrer">Hibernate</a> 3.x as the ORM tool</li> <li><a href="http://en.wikipedia.org/wiki/Spring_framework" rel="noreferrer">Spring</a> 2.5 for the business layer</li> <li><a href="http://wicket.apache.org/" rel="noreferrer">Wicket</a> 1.3.2 for the presentation layer</li> </ul> <p>I place a load balancer in front of the servers and a replacement load balancer in case my primary load balancer goes down.</p> <p>I use <a href="http://www.terracotta.org/" rel="noreferrer">Terracotta</a> to have the session information replicated between the servers. If a server goes down the user should be able to continue their work at another server, ideally as if nothing happened. What is left to "solve" (as I haven't actually tested this and for example do not know what I should use as a load balancer) is the database replication which is needed.</p> <p>If a user interacts with the application and the database changes, then that change must be replicated to the database servers on the other server machines. <strong>How should I go about doing that? Should I use MySQL PostgreSQL or something else (which ideally is free as we have a limited budget)? Does the other things above sound sensible?</strong></p> <p>Clarification: I cluster to get high availability first and foremost and I want to be able to add servers and use them all at the same time to get high scalability.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload