WAS.NEXT; It's got some spring in its feet.
gcuomo 060000X9CG Visits (4264)
The folks from SpringSourcecaused a buzz last week with an announcement of their SpringApplication Platform beta. An article on InfoQ,broke the story and my Inbox lit up like a Christmas tree. Subjectlines cited – “SpringSource is declaring war on WebSphere.”
Really? I don’t quite see it that way. Let me start by saying this…I’m a fan of Spring, and I think that a foundation of OSGi andtechnologies like Springframework are the future of Java-based applicationserving. The days of one-size fits all servers are evolving towardspurpose built servers that specialize in specific types of workloads(e.g., Web).
Java EE is astandards based “profile” that has served our customerswell for the past 10 years, and will continue to serve us. This isespecially true when you consider the shear number of JEE applicationsthat our customers have deployed over these years. But there are otherprofiles, for sure. For example, purposing servers as an EnterpriseService Bus, or a server that executes BPEL processes, or simplyprocesses Web requests - this is where we are heading. These server“profiles” are purpose build and right-sized for the task at hand.
In case you haven’t noticed, the WebSphere team, including AlanLittle, BillyNewport and IanRobinson, has been all over this (and have been recently bloggingabout this subject as well). WebSphere Application Server (WAS) v6.1shipped (~2 years ago) anEquinox-based OSGi core and bundles for key internal components. V7(openbeta now available) goes even further in making the move to a“schizophrenic ” application platform (i.e., an application serversupporting multiple application personalities), adding a service forexplicitly installing these purposed profiles. The WAS team has alsobeen focusing on integration with the Spring Framework, whichhas beencertified with WAS since V6.
So, again, this is where WebSphere and the industry were alreadyheading – no new news there.
Now, I do feel it’s a shame that SpringSource went off and did thisunder a GPL license.The industry would benefit from an Apac
This leaves plenty of room for capitalism. (After all, I do have afamily to feed). Fit for purpose plug-ins will provide the extendedvalue to our customer. The WebSphere-brand will major in providing“profiles” and quality-of-service (QoS) forthose profiles. This ispretty consistent with how we’ve built out the WebSphere (and much ofIBM Software Groups’) product-line. Specifically, we have long used WASas a general-purpose run-time, hosting a wide variety of products andfeatures including Process Server, ESB, Business Monitor, Data Grid,Portal, Commerce and much more. The OSGi+Spring combination will allowus to continue “right sizing” these products and more affectivelycreate our product combinations (E.g., our process server includes ourESB function). This architecture will also help support our wellreceived FeaturePacks, that allow new function to be incr
Our secret sauce, and the foundation for hundreds of patents andgenerally cool technology, has been in providing QoS for the WASfoundation, and the applications hosted on our servers; High Availably,Failure capture, Performance, Scale, Clustering, Monitoring, Trace andSystems Management are just of few of these features. Using techniqueslike “inversion of control”, we hope to also to insert to rightqualities for the right task.
Hence, the trend of evolving towards a platform with a righ
Come on then, this is my call to the Industry players; Let’s meet inOSGi and Apache and do it again. Certainly this is where WAS.NEXT is -who else wants to play?