Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
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.
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.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
7 comments
Watch Thread Reply