Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Stefan Tilkov on Jan 21, 2009
In an exclusive InfoQ article, IBM’s WebSphere CTO Jerry Cuomo outlines the 10 top technology direction he envisions for the WebSphere product line in 2009. The list consists of the following items:
Business Mashups refers to the idea of personalized, Web 2.0-style portals for business users; after the acquisition of iLog and AptSoft, IBM is busy integrating them into a consistent Business Rules strategy. Middleware as a Service refers to hosted Middleware, both supporting company-internal as well as public clouds. Rainmaker is Cuomo’s label for IBM’s general cloud support, including pre-built WebSphere AppServer images. Extreme Scale refers to high-performance transaction servers; WAS.NEXT is the next generation of IBM’s WebSphere Application Server, exploiting OSGi to enable a modular deployment. Cuomo also highlights REST support in WebSphere products such as CICS, WebSphere MQ, WAS, WSRR, Commerce, Portal, Process Server.
See the full article for more details.
Free $40 SOA Demystified Book Offer
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Visit SOA Appliance Comparison Site
*Video Usage Model Tutorials
*Comparison to IBM DataPower X150
*Performance Benchmarks/Webinars
*Replace DataPower Program
FREE 1:1 Swap & Migration Services
I fail to understand who could benefit from reading this kind of article.
If this has any reflection on IBM standards, then good luck!
I fail to understand who could benefit from reading this kind of article.
Hi Javaid, InfoQ covers current events in our space, so a letter by the CTO from IBM about what their plans are for Websphere is not just 'current' but forward looking. InfoQ is the only place where you can read this.
If this has any reflection on IBM standards, then good luck!
Given my track back has not shown up, here's a link to my response
JT
Websphere is getting bigger and bigger every year, I guess the same goes for the problems. If it is caused by
- inexperienced developers
- Websphere just getting too complex for mere mortals to understand
- nice individual technologies (like coherence) that never work well together
But Websphere environments are never something I'm looking forward to. Imho: too much baggage without providing value.
The baggage is very much a thing of the past. WAS6.1 started OSGi, WAS7 is mostly built from OSGi components declaring services except where some Open Source package has been "wrapped". Individual components can be started and stopped to have appropriate builds for appropriate uses (i.e. no EJB container, etc). I now, for the first time, think it is well architected. It is also dynamic in that deployment of components causes events that cause appropriate actions and reconfiguration in the runtime. WAS.NEXT allows some of this componentisation to be more "productised".
One other thing about this announcement - speaking as a customer - is that Jerry and his team have actually spent a great deal of time going out to the customers and architects, or working at a low level with the user groups, to find out what we wanted. A lot of these directions are as a direct result of the IBMers listening to customers, making proposals, getting feedback on the proposals, and then iterating the proposals into products.
So, I am pleased to see the content of this letter, and look forward to Rob High (Chief Architect and IBM Fellow) going into more detail at the WebSphere User Group conference in the UK next month.....
Just another soviet like propaganda article.
Could somebody provide GOOD customer feedback on any WebsFear product?
Most expensive, most unimproved, most buggy, most unstable, most complicated, most costly products...
- Black Hawk down... finally...
It's amazing that you would even bother to comment on a product with which you clearly have no recent experience.
IBM has made steady, continuous improvement to WebSphere with each release. In fact, I would have to say that the only thing I don't like is that their new feature pack strategy makes application of maintenance more difficult and time-consuming.
In the past several months, we've tripled the work that our WebSphere server is doing, and it's not even breaking a sweat.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
7 comments
Watch Thread Reply