New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Charles Humble on Jun 18, 2008
At this year’s Scotch on the Rocks conference Railo announced that they will become part of JBoss.org at Red Hat. Starting from the release of version 3.1 of their product, which is expected later this year, the professional version will be open sourced and released under the GNU Lesser General Public License (LGPL2).
Some Railo components such as the pdf generator (cfdocument) and the video playback (cfvideo) are licensed from third parties and cannot be open sourced, so there will be two versions of Railo - the aforementioned professional version, and an enterprise version with the additional features which will remain closed. Even so, the majority of the current engine and tag libraries will be released. As Sacha Labourey put it on his blog post covering the announcement:
“Just to make it clear, they are not going to open source just a “baby edition”. Instead, they will open source the complete codebase except a few components they are licensing from a thirdparty (such as the PDF generation and their online admin console) and which cannot be open sourced.”
The JBoss community will be contributing to the enhancement of core functionality, and are already exploring ways to integrate Hibernate and JBoss Cluster Cache directly into CFML. Railo may also be distributed with future versions of JBoss AS.
"JBoss has been a driving force behind the Open Source ecosystem built around the Java platform and in legitimizing Open Source Java middleware in the Enterprise", said Gert Franz, CEO of Railo, "and we believe that having JBoss.org as a community partner will dramatically increase the adoption and use of CFML in the enterprise market."
Given that CFML is tightly controlled by Adobe Systems it is unsurprising that Railo had talked to Adobe before they made this announcement, and the public reaction from Adobe has been very positive. Adam Lehman, Adobe’s chief evangelist for ColdFusion, said on his blog:
“Partnering with JBoss will expose CFML to the greater Java community. Additionally, CFML is now being recognized as a mainstream programming language by RedHat, a major player in the Enterprise space. There is nothing stopping a JBoss developer from dipping out of the JSP world to use a little CFML.”
Ben Forta, another Senior Technical Evangelist for Adobe, and well known amongst the ColdFusion community, gave a similarly up-beat assessment:
“Could the JBoss Railo relationship impact ColdFusion sales? Yes, of course it could. So why am I not worried about Railo's new announcement? Why do I think that this is actually a very positive direction? Because unlike some other relationships, this one does indeed have the best interests of the community at heart. Neither Railo nor JBoss see ColdFusion apps as legacy, and they don't see their only business model as in converting ColdFusion developers to Java or to .NET. Rather, they see the value that is CFML and the ColdFusion community, and they want to enhance it and expose it to the wider Java community. Which means that very realistically this relationship could significantly raise ColdFusion and CFML awareness, and could enhance ColdFusion's reputation and visibility, and could even help grow the size of the community and the number of deployments. And at the end of the day, if that were to occur, then the entire community would benefit, including ColdFusion and its customers and users.”
A number of third party ColdFusion tool vendors have also announced their support for the open sourced Railo product. Amongst them are Intergral, whose FusionReactor monitor product already supports Railo, and who have announced that they are working on a version of FusionDebug for Railo 3.1.
Railo is the third alternative CFML engine to be open sourced - the creation of OpenBD and The Smith Project both pre-date the announcement. But the choice of LPGL, meaning that developers will be able to bundle Railo's engine in their own products even if they are closed source, and the positive reaction from Adobe, make it a particularly interesting announcement.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read 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.
No comments
Watch Thread Reply