JAX London 2014: A retrospective
Hyperic 4.5 Interview

Hyperic Product Manager on Version 4.5

Jessica Thornsby
Hyperic-Product-Manager-on-Version-4-5

“A single developer coding and debugging an application now saves approximately 5 minutes of waiting each time he/she starts up the application.”

  • Al Sargent

    Al Sargent is a Senior Product Marketing Manager within the Application Platform Division at VMware. In this role, he works closely with VMware engineering teams towards the continued delivery of Hyperic and other products. Prior to joining VMware, Al held product and engineering roles with Wily Technology (now part of CA), Mercury Interactive (now part of HP), Oracle, as well as leading venture-funded cloud computing and SaaS startups. Al holds a Bachelor of Science, Symbolic Systems, from Stanford University, and an MBA from UCLA Anderson School of Management.

JAXenter speaks to Hyperic Product Manager Al Sargent, on the latest release…..

JAXenter: Hyperic 4.5 upgrades the codebase to Spring 3.0. What benefits does this bring to the user?

Al Sargent: By switching from JEE to Spring, the Hyperic team is able to work more efficiently by reducing code complexity and improving testability, which in turn enables them to increase the velocity of new features they can deliver to users. You can read more details at the SpringSource blog.

JAXenter: What motivated the Hyperic team to switch from JBoss to Apache Tomcat, for this release?

Al Sargent: Developer productivity played a big role. For example, the switch to Tomcat has improved our productivity by significantly decreasing startup time. A single developer coding and debugging an application now saves approximately 5 minutes of waiting each time he/she starts up the application. Considering that the developer may restart the application 12 times a day, it frees up an entire hour per day to develop new features.

JAXenter: What features are planned for future releases?

Al Sargent: We are quite excited about the Hyperic roadmap, but we cannot provide details at this time.

Author
Comments
comments powered by Disqus