Agile and Beyond - The Power of Aspirational Teams
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Tracking change and innovation in the enterprise software development community
Posted by Johan Strandler on Jul 30, 2007 09:40 AM
Since the acquisition of Logicblaze in april, things have been quiet with regards to what shold happen with the Logicblaze open source SOA product FUSE. Last week however, IONA presented their open source strategy roadmap by announcing a merger of the former Logicblaze FUSE product and IONAs own Celtix product. The new open source product line will keep the FUSE brand and will consist of four product modules that can either be deployed together or independently:
The merger of the products has lead to some exclusion from both of the earlier products. From the Celtix product an AMQP implementation based on the Apache Qpid project has been removed. From the Logicblaze FUSE, a BPEL engine based on the Apache ODE project, an UDDI registry, the Jetty Web server and the Liferay portal has been removed.
Commenting in the FAQ on the removal of the AMQP and Qpid implementation, IONA "...choose to postpone their commitment for commercial support until they gain greater maturity and market traction". As for the removal of the BPEL engine in their new open source product line, IONA says that they "...encourages the use of any JBI-compliant BPEL engine with the FUSE ESB". For those that "...aren't happy with the open source options, IONA does provide the Artix Orchestration product".
Given the announcement, it seems that IONA has chosen a business model for open source similar to the one IBM uses for it's WebSphere product line, which includes one proprietary product line plus a complementary open source alternative through the WebSphere Application Server Community Edition. IONA now pushes the Atrix proprietary product line and the open source alternative FUSE.
From this announcement we see that the Java Business Integration (JBI) path started early on by Logicblaze has a firm continuation within IONA. The FUSE ESB should be able to function as the JBI based glue between FUSE products as well as to other products. Another interesting point is the inclusion of of the new Apache Camel project used in the FUSE Mediation Router product. Apache Camel is a rule based routing and mediation engine which provides a POJO based implementation of the Enterprise Integration Patterns.
The End of Middleware: Freedom from IT Stacks as we know it
Real World REST & Document-Oriented Distributed Databases Tracks @ QCon SF Nov 19-21
The Agile Business Analyst: Skills and Techniques needed for Agile
Rainmaking - IBM's software virtualization strategy (Jerry Cuomo CTO blog)
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
No comments
Reply