Recently, VMware Senior System Engineer, John Ferguson, penned an article, captured a how-to video, and provided a full presentation on agile servers for Java runtimes. He uses vFabric’s Tomcat Server in the examples and shows how to get this lean server up and running in 60 seconds.

As an expert in enterprise systems and Agile development with Java, John starts by connecting one of the most misunderstood concepts in IT today—technology debt. What is technology debt?

Technology Debt

Technology debt is a sophisticated term with a simple explanation. Technology debt is debt caused by all the systems we refer to as spaghetti code, ducktape and bailingwire, or just plain crappy development. These are the systems no one wants to touch because of the sheer number of grey hairs they cause and the volume of aspirin intake they initiate. 

Here is how technology debt happens—we get too busy or have some other pressures that prevent us from doing the job with high quality in mind. In the end, we have to pay to play—to change a line of code, the codebase needs to be updated in 10 other places. We pay a debt to make a new investment.  

As developers, we see these types of circumstances create technical debt:

  • Business pressures to add features on tight timelines
  • Tightly coupled components from a lack of architecture planning
  • No documentation and turn-over on development teams
  • Parallel development that eventually must merge

Paying Back Technology Debts

John goes on to explain how debt avoided with agile development approaches and runtimes. In the case of runtimes, John dives deep into the use of tc Server, Hyperic, Elastic Memory for Java (EM4J), and other VMware and open source tools to get Agile development runtimes in place. The 42 minute video is an excellent resource for developers who want to overcome barriers to agile business and development practices.

How To Guide—Lean Servers and Practices

In the video, John shows us how to get tc Server up and running on a VM in 60 seconds. He also covers the difference between paying for average use and peak use, compares traditional J2EE services with lean servers, stays on the topic of driving operational efficiency, explains monitoring, and more.

To see the full article, video, and more, read the full article.