PART 1 | PART 2 | PART 3
Despite the popularity of Tomcat, it seems to have something of a reputation for being a developer’s application server because of how apparently simple and “no-frills” it seems to be, and therefore suited only to the most lightweight of deployments. In reality, many of the features that aren’t included in Tomcat are those that most businesses will never miss (and for those that will, projects like TomEE bring together all the necessaries for a full Java EE profile).
In this blog post, I’ll go through a very common scenario for a small production environment – a single tier, load balanced application server cluster.
One of the most fundamental concepts in high availability is load balancing work across multiple server instances. The specifics of exactly how that is achieved varies a lot depending on whether you want to scale up – add more server instances to a host – or scale out – add more hosts with server instances on.