Load Balancing PostgreSQL or EnterpriseDB
We have been working on a large project since March, converting a client off of Informix to a modern version of PostgreSQL. For various reasons, we chose to use the enterpriseDB version of PostgreSQL, which packages the latest version of the core database with tools to do replication (Slony-I) and management (DBA Management). Just recently, I purchased Silver level tech support for our project, priced at a very reasonable $1,000 per CPU.Our goal for the conversion was to change the core of the application (almost 275,000 lines of Java code) as little as possible. Of course, we are re-architecting some aspects of the application to increase redundancy and performance while we were migrating the database. One aspect of improvement is migrating from a single server to three different servers. Each server has a replicated database copy running on it, and we would like to use a load-balancer between the three (pgpool). To ensure that the web application (Java running inside of Tomcat) was not the single point of failure, we are replicating the web application on all three as well, using a firewall appliance to choose between the three application layers.
Additionally, we have rewrite more than 80 reports from Informix's 4GL to Crystal Reports and Jasper Reports (we use both) and handle minor differences between the two database backends (including datetime differences).
0 Comments:
Post a Comment
<< Home