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 Mark Figley on Oct 18, 2007
A new Gartner report, Trends in Platform Middleware: Disruption Is in Sight, highlights some disruptive elements that threaten the currently dominant middleware platforms. Amongst those disruptive influences, EDA (Event Driven Architecture) was prominently identified as an alternative approach to more traditional component based architectures. The paper's authors see EDA moving from vertical industry support to general purpose business critical application architectures, thereby driving a new wave of adoption:
EDA support will be integrated into general-purpose platform middleware and will become an essential ingredient in most new enterprise-class, business-critical projects. EDA will foster innovation not only in platform middleware but also in packaged applications, development tools, business process management and monitoring, and other software industry sectors.
Combined with the trend towards SOA, these emerging programming models represent a significant threat to traditional middleware vendors. Even with all of the work from vendors to make the Java EE and .NET platforms support the SOA programming model, the authors see both SOA and EDA as key drivers away from these platforms and towards new programming models:
...mainstream programming models' limited support for increasingly popular SOA and EDA styles is becoming more apparent. Conceived in the late 1990s to support Web applications, these programming models have absorbed basic SOA and event-processing capabilities, but these are bolted-on features that further complicate already-complex programming models.
As alternatives, the Gartner report highlights the Service Compnent Architecture (SCA), Service Data Objects (SDO), EDA, BPEL, and Windows Workflow Foundation (WWF) as emerging programming models that will eclipse the more traditional component based programming models that dominate both Java EE and .NET today.
Another significant theme of the paper was the impact of open source, and especially the Spring Framework, on the middleware space. And far from being a lower-cost, lower-capability alternative, these alternatives are emerging as first class options that sometimes exceed the capabilities of the traditional offerings.
Somewhat surprisingly, XTP (Extreme Transaction Processing) was identified as one of the driving forces behind the adoption of both Spring and OSGi. But while the performance and reliability of Spring certainly doesn't hurt, the primary driving force behind Spring adoption is still the simplified programming model it provides. As Java EE and .NET have both bloated in complexity, Spring provides a critical foundation for simplified enterprise development. And Spring is so effective that it is making some wonder if the traditional application server is even necessary:
Although most established Java EE vendors support Spring, its increasing industry adoption is a potential threat to its now-dominant role as this adoption paves the way for alternative, non-Java-EE-compliant platforms.
The open source application servers were also mentioned. Red Hat's JBoss still leads this space, with both Glassfish and Geronimo growing in adoption. IBM's support for Geronimo and BEA's support for Spring were both seen as confirmations of the validity of open source options for infrastructure middleware. This in turn will increase the trend towards commoditization and put further price pressure on traditional middleware platforms.
Lastly, the increasing relevance and adoption of dynamic languages and RESTful services were recognized as low impact trends. While they may significantly change the way developers build applications on top of these platforms, they will probably have less of an impact on the choices organizations make when selecting the middleware itself. Both of these trends also represent the broader industry trend towards simplification that is also behind the success of Spring and the recent direction of the Java EE spec itself.
The full paper is available to Gartner subscribers or for purchase. What do you think about Gartner's points?
Ughh, I wrote another comment on the exuberance of Spring-support, but I figure that has been covered enough already....Gartner is just an analyst that is in the hat of WebSphere and WebLogic and will perpetuate the long-standing belief that only those two are relevant despite paying admirable and over-due lip-service to JBoss, Glassfish, and Geronimo...all 3 which now control the app server debate....
SCA and Spring are contenders to JEE, but to overlook comprehensiveness of spec., installed base, and community involvement to suggest that the disrupter is anything but JEE5 is nonsense to me...I would suggest Yefim and Co. write a follow-up (dont buy Gartner reports, so maybe they have) to give customers the true view on where investments are most advisable beyond the departmental-level experiments....
This Spring v. JEE5 debate is compounded by supposed SCA legitimacy, amd I the only one who just doesn't see it?
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.
1 comment
Watch Thread Reply