
Continuous Delivery on Kubernetes using Jenkins X
Thursday, February 28, 2013
Get ready for CamelOne 2013!!

Monday, February 04, 2013
What's the Future for Fuse at Red Hat ?
Its been just over five months since Red Hat acquired FuseSource, and that isn't a long time for an acquisition to find its feet, but Red Hat is an open source company, and shares a lot of the same culture and values that FuseSource did, which has made thing considerably easier.
FuseSource was a separate legal entity and run successfully as an independent company, but its biggest share holder was its former host Progress Software. When Progress lowered its sights last year, and changed its strategy, it very publicly announced its intention to divest a large number of its products including SonicESB, SonicMQ, DataXtend, Savvion BPM, Orbix etc. FuseSource was also bundled into that mix. To be honest, being put up for sale by the good folks at Progress was a shock: FuseSource was growing fast, had a large number of top brand customers and was out performing its open source competitors by some margin. You would expected revenues to fall off a cliff - but for us they didn't - we kept growing and that trend is accelerating now we part of the JBoss family at Red Hat.
What has caused some confusion is that FuseSource had well established products for messaging and integration, but so does Red Hat JBoss. There was an assumption that these products will get folded together, but they actually address different users. JBoss has a comprehensive SOA story, but SOA isn't integration:
Fuse ESB Enterprise (which is based on Apache Camel, ActiveMQ, CXF and Fuse Fabric) will be able to work in conjunction with the JBoss SOA platform, and they will both share some of the same open source technologies. Fuse ESB Enterprise is going to be rebranded JBoss Fuse, for the upcoming release in Q2 this year, and as previously announced, the developer tooling has now been open sourced:
We aren't going to stop at rebranding though, development of future enhancements to the JBoss Fuse product have already started, its a product that will continue to evolve and has a very bright future a head of it.
Fuse MQ is also getting re-branded to JBoss A-MQ. The release in Q2 of this year is going to be based on Apache ActiveMQ 5.8, the biggest change to this release is the addition of AMQP 1.0 support:
Red Hat JBoss has more than one messaging product and over time this is going to get more consolidated, as we look to provide a messaging architecture that will last to 2020 and beyond. There is an accelerating demand for high performance, lower latency and scaling out to millions of concurrent connections. To be able to do that in a way that leaves none of our existing customers and users behind is going to take a while to get right - but we will do it.
So what's the future for Fuse at Red Hat ? A great one!
FuseSource was a separate legal entity and run successfully as an independent company, but its biggest share holder was its former host Progress Software. When Progress lowered its sights last year, and changed its strategy, it very publicly announced its intention to divest a large number of its products including SonicESB, SonicMQ, DataXtend, Savvion BPM, Orbix etc. FuseSource was also bundled into that mix. To be honest, being put up for sale by the good folks at Progress was a shock: FuseSource was growing fast, had a large number of top brand customers and was out performing its open source competitors by some margin. You would expected revenues to fall off a cliff - but for us they didn't - we kept growing and that trend is accelerating now we part of the JBoss family at Red Hat.
What has caused some confusion is that FuseSource had well established products for messaging and integration, but so does Red Hat JBoss. There was an assumption that these products will get folded together, but they actually address different users. JBoss has a comprehensive SOA story, but SOA isn't integration:
Fuse ESB Enterprise (which is based on Apache Camel, ActiveMQ, CXF and Fuse Fabric) will be able to work in conjunction with the JBoss SOA platform, and they will both share some of the same open source technologies. Fuse ESB Enterprise is going to be rebranded JBoss Fuse, for the upcoming release in Q2 this year, and as previously announced, the developer tooling has now been open sourced:
We aren't going to stop at rebranding though, development of future enhancements to the JBoss Fuse product have already started, its a product that will continue to evolve and has a very bright future a head of it.
Fuse MQ is also getting re-branded to JBoss A-MQ. The release in Q2 of this year is going to be based on Apache ActiveMQ 5.8, the biggest change to this release is the addition of AMQP 1.0 support:
Red Hat JBoss has more than one messaging product and over time this is going to get more consolidated, as we look to provide a messaging architecture that will last to 2020 and beyond. There is an accelerating demand for high performance, lower latency and scaling out to millions of concurrent connections. To be able to do that in a way that leaves none of our existing customers and users behind is going to take a while to get right - but we will do it.
So what's the future for Fuse at Red Hat ? A great one!
Friday, February 01, 2013
History of Open Source
I gave a talk last year at Walmart HQ about Fuse open source integration and messaging, the benefits of using open source and the benefits of contributing to the Apache Software Foundation. You can find a sanitized version on slideshare.net.
I also covered the history of open source, and like all histories there is no one 'right' story, but I tried to distill the timeline as best I could. On the chance this may be useful to someone else I tell the story here. Are you sitting comfortably? Then I'll begin ...
The IBM 704 was the first mass produced computer with floating point arithmetic hardware and was introduced to the fledgling computer market back in 1954. IBM managed to sell a whopping 123 of these beasts between 1955 and 1960. IBM bundled these machines with free software and source code - and in 1955 the organization SHARE was formed to allow like-minded individuals to share and swap code for the 704 machine. SHARE is the first public open source organization, and is still around today.
Everything was really rosy in open source land (though not good for IBM competitors) - until in 1969 the Department of Justice filed a suit alleging that IBM was monopolizing the computer market. The suit dragged on for 13 years, but the effect of the filing was that in 1969 IBM unbundled its software from distribution with its computers. Until this point, the software was free and the source code was distributed too.
Now we diverge in to the 70's-80's, and the UNIX wars, which are only slightly less hard to follow than the War of the Roses - so I'll try and distill the salient points.
UNIX started its development in the 1960's as Multics, at Bell Labs, which was then part of AT&T. Originally written in assembly language, it was ported in 1972 to the C programming language - allowing it to become more portable. AT&T were banned from selling computers and computer software - as result of an antitrust case brought back in the 1950's. UNIX was freely licensed to Universities and educational establishments, and became the Berkley Software Distribution (BSD) - first released by University of Berkley in 1984.
On a tangent timeline, in 1983 Richard Stallman creates GNU (GNU is not UNIX) which will lead to the Free Software Foundation and the the GPL (and LGPL) licenses.
Jumping back to 1984, US regulators broke up AT&T into regional telcos (the "baby bells"), but also allowed AT&T to enter the computing and software market, and to start selling its own distributions of AT&T UNIX, which it did aggressively. When AT&T sued Berkley in the early 90's for license violations, the UNIX market was left in disarray.
From every conflict, there is opportunity, and Linus Torvalds' development of LINUX in 1991 started an open source fire, which ultimately led to the most successful open source company, Red Hat, coming into existence.
The Apache HTTP server started in 1994 from the requirement to maintain the old NCSA HTTP daemon. This collaboration led to the Apache Software Foundation in 1999.
The biggest revolution in open source has come about through the creation of GitHub (2008) - which just narrowly gets my vote as being the most important company in open source development, primarily because it uses social networking techniques to encourage collaboration - and in just a few short years has over 1 million users and over 2 million repos.
So we come full circle, with Gartner predicting that open source software will be included in mission critical software portfolios of 99% of the Global 2000 enterprises.
I also covered the history of open source, and like all histories there is no one 'right' story, but I tried to distill the timeline as best I could. On the chance this may be useful to someone else I tell the story here. Are you sitting comfortably? Then I'll begin ...
The IBM 704 was the first mass produced computer with floating point arithmetic hardware and was introduced to the fledgling computer market back in 1954. IBM managed to sell a whopping 123 of these beasts between 1955 and 1960. IBM bundled these machines with free software and source code - and in 1955 the organization SHARE was formed to allow like-minded individuals to share and swap code for the 704 machine. SHARE is the first public open source organization, and is still around today.
Everything was really rosy in open source land (though not good for IBM competitors) - until in 1969 the Department of Justice filed a suit alleging that IBM was monopolizing the computer market. The suit dragged on for 13 years, but the effect of the filing was that in 1969 IBM unbundled its software from distribution with its computers. Until this point, the software was free and the source code was distributed too.
Now we diverge in to the 70's-80's, and the UNIX wars, which are only slightly less hard to follow than the War of the Roses - so I'll try and distill the salient points.
UNIX started its development in the 1960's as Multics, at Bell Labs, which was then part of AT&T. Originally written in assembly language, it was ported in 1972 to the C programming language - allowing it to become more portable. AT&T were banned from selling computers and computer software - as result of an antitrust case brought back in the 1950's. UNIX was freely licensed to Universities and educational establishments, and became the Berkley Software Distribution (BSD) - first released by University of Berkley in 1984.
On a tangent timeline, in 1983 Richard Stallman creates GNU (GNU is not UNIX) which will lead to the Free Software Foundation and the the GPL (and LGPL) licenses.
Jumping back to 1984, US regulators broke up AT&T into regional telcos (the "baby bells"), but also allowed AT&T to enter the computing and software market, and to start selling its own distributions of AT&T UNIX, which it did aggressively. When AT&T sued Berkley in the early 90's for license violations, the UNIX market was left in disarray.
From every conflict, there is opportunity, and Linus Torvalds' development of LINUX in 1991 started an open source fire, which ultimately led to the most successful open source company, Red Hat, coming into existence.
The Apache HTTP server started in 1994 from the requirement to maintain the old NCSA HTTP daemon. This collaboration led to the Apache Software Foundation in 1999.
The biggest revolution in open source has come about through the creation of GitHub (2008) - which just narrowly gets my vote as being the most important company in open source development, primarily because it uses social networking techniques to encourage collaboration - and in just a few short years has over 1 million users and over 2 million repos.
So we come full circle, with Gartner predicting that open source software will be included in mission critical software portfolios of 99% of the Global 2000 enterprises.
Subscribe to:
Posts (Atom)