Nitin has posted 391 posts at DZone. View Full User Profile

SpringSource Acquires Hyperic

  • submit to reddit

SpringSource today announced that it has acquired Hyperic, expanding its reach into the datacenter and application management space. At SpringOne last month, SpringSource unveiled the SpringSource tc server, an Apache Tomcat retrofit that adds enterprise capabilities to the web server such as application management, server configuration, and advanced server diagnostics. 

With today's announcement, SpringSource deepens its runtime portfolio -- Hyperic's open source, web application performance management software manages and monitors the availability of everything from hardware and operating systems, to virtual machines, databases, and application servers.  Today's acquisition brings numerous Fortune 1000, SaaS and consumer web companies into the SpringSource customer base.

The Hyperic acquisition completes SpringSource's vision to provide a complete end-to-end solution and positions the company to go head-to-head with other paltform players like of IBM and Microsoft, according to CNET's Matt Asay

“SpringSource is taking responsibility for streamlining enterprise Java to fully cater to the needs of developers, IT administrators and operators who create, deploy and manage business-critical applications,” said Rod Johnson, SpringSource CEO. “The acquisition of Hyperic enables SpringSource to provide a complete, proven suite of lean application infrastructure software products that enable enterprises to accelerate the build, run, and manage application lifecycle within the data center, virtual, or cloud computing environments.”

SpringSource has come a long way from its development roots and focus on the Spring Framework to becoming a serious contender in the application platform space. What are your thoughts on the evolution of the company? Is it heading in the right direction?

Published at DZone with permission of its author, Nitin Bharti.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Jim Bethancourt replied on Mon, 2009/05/04 - 10:57pm

As far as thoughts on the evolution of SpingSource, I would have to guess that Terracotta might be a company of interest. Terracotta has done an excellent job of making it easy to scale out enterprise applications, and made it very easy to monitor those applications through Hyperic.

Given that

  • SpringSource and Terracotta are partners
  • A majority number of Spring-based applications run in an enterprise environment
  • Terracotta provides an out of the box Spring integration solution (complete with a reference app)
  • SpringSource is working on becoming a one-stop vendor for development, deployment, and management of enterprise applications
effortless scale out is pretty much the only thing missing from SpringSource's solution. Given this, it would make sense to see their relationship deepen even further.

Andrew McVeigh replied on Tue, 2009/05/05 - 7:27am in response to: Jim Bethancourt

terracotta would be an awesome acquisition, placing them in the same space as Coherence but with a better application story.

p.s. is anyone else finding the constant stream of Spring-related marketing announcements a bit tiring? e.g.  They are starting to reach fever pitch hyperbole with statements like "SpringSource going after MS and IBM (the big giants are quaking in their boots...)" I'd be suprised if MS even know who SpringSource are.

Rambo Ramalama replied on Thu, 2009/05/07 - 1:22am

Do you and your career a big favor, and ignore Spring completely. Spring may have some nice libraries, but a good deal of it is basically bloat. I for one escaped (whew!!) wasting about a year externalizing all my beans in reflecto injector code (now better put into annotations -- and the annotations can be automatically externalized into XML anyway). I remember (not so fondly) debugging some Spring JDBC wrappers (totally useless) once. When I tried to get answers from the other developers as to just exactly why we were using spring, all I could get was blank stares. The basic assumption behind Spring is "well, the Java libraries need all this extra wrapper code to make is usable". At least, that's what it seems to be saying. Show me a Spring app and I'll show you another app that is easier to understand and maintain without Spring. Spring makes extensions to the core libraries by writing APIs that "wrap" access to the core libraries. Therein lies several assumptions: 1. The original developers of the API didn't "see" how it "really should have been written" (sometimes the case) 2. There are no other requirements that will be hidden or made more difficult by this wrapper around the base API, or that they will be so few that the advantages of the wrapper outweigh any risks (rarely the case). The main problem is assumption number (2) above. The new APIs often hide something, basically forcing the developer to learn the original API (which is what she would have done in the first place, without Spring) as well as the Spring 'improvements'. Spring is like injecting Java with steroids, the only problem is, the steroids are made in a wacky laboratory and all the genetic sequences are backwards, so you end up getting something that looks like Frankenstein's monster with the organs on the outside.

Alexander Shirkov replied on Fri, 2009/05/15 - 9:51am in response to: Rambo Ramalama



So offensive.

Your basic assumption behind Spring "well, the Java libraries need all this extra wrapper code to make is usable" is totally wrong. In reality it's sounds like: Spring wraps all "mechanical, repeating" parts and let you focus on business instead of handling connection, catching exceptions, etc.

In most cases Spring speeds up development. Your main mistake in your "assumptions" - you thinl, that developers don't know APIs in the back. That's wrong. In most cases you HAVE TO know it to do job in effective way. You "Frankensteins" is only related to you, don't stick all of us in one bundle.

P.S. JDBC wrappers are really cool - you just don't know, how to cook them.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.