Alfresco recently released some information about its enterprise content management system user base. This study was picked up in several articles including eWeek. It shows a strong Red Hat presence in these Alfresco enterprise deployments and user base.
One of the most interesting tidbits of news was the fact that JBoss Portal had a strong lead in deployments using a Portal with 51% share. Liferay was a distant second at 32% and closed source Portals could only garner 17% share collectively! Looks like another market moving to open source!
I represented Red Hat at the US version of the Accenture conference that Mark Little attended in Europe and blogged about. As Mark described, it was a good conference and basically the same questions and discussion took place. On the vendor panel was IBM, BEA, Red Hat, Microsoft, Sun and Oracle in that seating order. However, there were a couple of notable differences.
For one, while I extolled the importance of vendor-driven standards to solve complex business problems (and reiterated Red Hat's participation in these activities), I also mentioned that I continue to be amazed at how super star developers create a framework such as Hibernate, jBPM, Drools, Spring, or Seam to solve a programming problem in a simple way that ends up being used by large numbers of developers creating a defacto standard. This got a rise out of at least one of the commercial vendors who went on to say something like this after describing their leadership driving standards - "...and these open source communities are proliferating creating way too many frameworks and projects. Like JBoss Seam. Why don't we just fix JSF through the vendor process? Some of these open source projects become defacto standards! I hate to say this, but we need to stifle creativity in the open source community and control these standards so they evolve in a more orderly way...". Wow! I fell out of my chair...and grabbed the mike :-)
After answering the question about open source evolution, I went on to say something like..."While the vendor driven standards process is important, that process gave us J2EE entity beans and the open source community gave us Hibernate. I need say nothing further!".
Oh, and how did I answer "How do I see oen source (OSS) evolving"? Basically, OSS is bringing a great deal of energy and creativity solving developer and business computing problems. OSS is expanding the market by making software more affordable and higher quality. As OSS SOA middleware evolves and becomes more feature rich, it is putting pressure on the commercial vendors in the manner described in the "Innovator's Dilemma" where commercial software continues to become more complex and overrshoots more and more of the market with open source taking a greater share over the next decade.
It was a fun panel :-) .
Not long ago, business rules engines were one of the bastions of pure academic computer science with only a niche role in serving business. As applied artificial intelligence, rules engines are the domain of PhD academics and were used in some advanced simulations, etc... No more. With the rise of some of the pioneering vendors and now a leading open source contender, JBoss Rules, rules engines are being embedded in web applications as well as providing services in a service-oriented architecture (SOA) and to business processes automated with business process management (BPM).
JBoss Rules is the Red Hat product that combines the Drools project with a JBoss subscription. JBoss Rules 3.X was the first version offered by Red Hat's JBoss division starting in early 2006 and was focused on developers using a rules engine embedded in their web or enterprise application. Now, with JBoss Rules 4.0, we see open source rules moving into larger business process roles with its business analyst-friendly business rules management system (technology preview) and more rules tools advancements such as the guided editor. JBoss Rules 4.0 lays the foundation for bringing rules-based solutions into Simple, Open and Affordable SOA deployments and business process workflows.
JBoss Rules 4.0 adds numerous capabilities including:
These additions have been created working with the Drools project user and developer community and shows the power and speed that open source development brings to bear on a high value middleware segment such as rules engines. We are excited about the progress of JBoss Rules and the expanded opportunities it offers for developers and business process professionals around the world!
Check the latest Drools release. Learn more about Red Hat's JBoss Rules product and here which includes the Drools project and the JBoss Subscription. We expect JBoss Rules 4.0 to be finalized by July 20th.
JBoss Portal 2.6 builds on the JBoss open source tradition of collaboration with our users, customers and developer community simplifying user interaction and participation in service-oriented-architecture-enabled business processes. JBoss Portal continues to see expanding deployment in customer service and intranet portal deployments where a simpler, more open and affordable platform is required. The telecommunications, financial services, government and other industries see the benefits of using open source software to add value to their SOA deployments by delivering to human business process participants a personalized experience improving their productivity doing their jobs.
The main themes of JBoss Portal 2.6 community developed enhancements include the following:
We are excited about the possibilities for customers and users to improve user experiences with JBoss Portal 2.6. In particular, the personalization, usability, identity and WSRP enhancements take JBoss Portal to a new level that was driven by our customers and community for their own use. Check out JBoss Portal and create better user experiences for you and your users today!