Private vs Shared Java Web Hosting
Tomcat is written in Java and runs in a Java virtual machine (JVM). At startup. the JVM reserves for itself a fixed amount of memory for dynamic
allocation (its heap). Whichever users are using that Tomcat instance are using that same heap.
You can think of the JVM and its heap as being like a swimming pool. Things are put in, things are taken out and every so often it gets cleaned. A
shared JVM is like being in a crowded public pool - you're swimming in whatever the crowd puts into the pool. A private JVM is like having a
crystal clear swimming pool in your own back yard, restricted to only that which you put into it. To get instant, free setup of your own private
JVM Tomcat server, signup for our
Java Web Hosting now.
Looking at it technically, the two biggest problems with shared JVM hosting are memory leaks and security.
If someone has a memory leak or code that is a high user of memory in a shared environment, all of the people sharing that JVM suffer the same
memory problems. Memory issues can range from server slowdowns to out of memory exceptions which can freeze the server - usually until a human notices
the problem and restarts the engine.
A bad actor causing security problems within a shared JVM, whether by intent or not, is putting every user of the space at risk.
Just because Tomcat is a very secure server with finely grained controls, doesn't mean that you want to give others the keys to your house with your
work product sitting out on the kitchen table.
Our marketing surveys show that the price difference between the cheapest shared Tomcat hosting and our private Tomcat hosting is about $9 per month.
If your code is worth more to you than those nine dollars,
try private JVM Tomcat 6 Hosting without risk - you'll receive a
complete refund if you are unsatisfied. To learn more about our Java web hosting, go to our
Java hosting plans compared.