Matt RaibleMatt Raible is a Java Champion and Developer Advocate at Okta.

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

Groove Systems: Cheap Java Hosting Provider

Spotted on the WebWork Mailing List today. Groove Systems (Rick Salsa's employer) has some nice hosting solutions. I currently pay $30 (Canadian) for 200 MB, 5 GB Transfer and my own JVM at Keith (at KGB) rocks because he is always quick to respond to any of my issues and always tries to help me out. However, I have to admit, Groove's Grooviest package looks pretty nice. For the same price ($30 Canadian), you get 1 GB space, 15 GB Transfer and your own JVM.

The only question I have is how much memory do you get? Keith does nothing to limit memory usage, so I'm currently set at a 512 MB max heap size. Who knows if I'm using it all, that's just what I'm set at. Oh and one other thing you might like to know:

... right now you can get a 32meg private jvm for free.

Read the read e-mail from Rick for more info.

Posted in Java at Mar 10 2004, 12:54:11 PM MST 3 Comments

anyone know what the benefit of having a private jvm is and how to figure out how large of a heap size is needed for a particular app?

Posted by Francisco Hernandez on March 10, 2004 at 02:21 PM MST #

The benefit is that someone elses web app written using JSF can't crash your web app... ;-)

Posted by Jason Carreira on March 10, 2004 at 04:27 PM MST #

Jason's right. Also add on the fact that you won't have to wait until after hours to have your provider restart the shared jvm. You can stop and start it anytime you want. You can estimate the your needed heap size using this approach: 1. Start your container with no starting heap (no -Xms argument) and a large maximum heap size (-Xmx argument). 2. Run a test script that brings your application to its maximum throughput level. 3. Determine what size your JVM heap size grows to under maximum load. 4. Set both the starting heap and maximum heap to a level larger than that to which the JVM heap grew naturally under load. For most of the sites we host, they are doing fine with 32megs. HTH, /rick

Posted by Rick Salsa on March 10, 2004 at 05:23 PM MST #

Post a Comment:
  • HTML Syntax: Allowed