Wily Technology (www.wilytech.com) provides Enterprise Application Management solutions. The company's products are designed to enable companies to successfully manage their critical Web applications and infrastructure by providing real-time, end-to-end visibility into the performance and availability of these systems. Wily Technology is based in Brisbane, California, just south of San Francisco. WJ's former Editor-in-Chief Jack Martin had a chance recently to sit down with company CEO Dick Williams.
WebSphere Journal: Give our readers a quick overview of what Wily Technologies is all about, if you could.
Dick Williams: Wily allows customers to develop and deploy major Web applications more rapidly and assuredly, and to keep them performing optimally.
WJ: Sounds simple enough, yet your strategy inside of the WebSphere space is unique compared to the other vendors. Could you explain that?
DW: Our strategy is really focused on providing unique functionality to WebSphere customers that allows them to deploy major business-critical WebSphere-based applications reliably, predictably, and rapidly. They could be application server-based; they could be written directly to a JVM; they could be portal applications; they could be integration applications; they could be end-user facing applications; or they could be infrastructure. In all cases we want to allow them to predictably and rapidly deploy those applications and then to keep them in production performing optimally.
WJ: You also have an interesting story in that your products are 100 percent pure Java. Why did you do that?
DW: This is a key part of our current core architecture and technology in that we operate today entirely in the Web space, and largely in the J2EE or Java space. Java actually has matured to do all of the things it originally was designed to do, and enterprises trust it as the core for their complex, business-critical applications. So when you create a complete native Java application, then you inherit an enormous number of capabilities and functionalities. One of the most important is platform support and homogeneity across those platforms. A result of that is we can do a single implementation of a product or functionality, and then immediately the customer is able to deploy it on all Java supported application servers, JVMs and all Java supported platforms. Same identical product, same day, same identical functionality.
WJ: How do you accomplish that?
DW: We do that by adhering to our core architectures and by adhering to the J2EE Java standards. You know that your typical application software team will spend 20 to 30 percent of their time, resources and money on ports-developing, testing and documenting ports. We spend about two percent. Subsequently, we're able to devote that other 18 to 28 percent advancing the product and better serving our customers.
WJ: So the money you are saving by being pure Java you are rolling back into the product?
DW: Absolutely.
