Inside the Briefcase

IT Briefcase Exclusive Interview: The Tipping Point – When Things Changed for Cloud Computing

IT Briefcase Exclusive Interview: The Tipping Point – When Things Changed for Cloud Computing

with Shawn Moore, Solodev
In this interview, Shawn Moore,...

Driving Better Outcomes through Workforce Analytics Webcast

Driving Better Outcomes through Workforce Analytics Webcast

Find out what’s really going on in your business...

Legacy Modernization: Look to the Cloud and Open Systems

Legacy Modernization: Look to the Cloud and Open Systems

On the surface, mainframe architecture seems relatively simple: A...

Still keeping your hybrid power systems indoors?  It’s time for change.

Still keeping your hybrid power systems indoors? It’s time for change.

Mobile telecommunications network equipment is expected to work without...

As the Network Changes, Engineers Are Embracing the DevOps Model

As the Network Changes, Engineers Are Embracing the DevOps Model

Businesses that have embraced digital transformation with a clear...

FuseSource Continues Strategy Of Support For Apache Projects

April 12, 2011 No Comments

SOURCE:  Network World

Back in October I wrote about a new spin off from Progress Software called FuseSource. They are trying to do with Apache Projects what Red Hat has been able to do with Linux.  I like the company because they are very clear on what their mission is. They don’t consider themselves “open core” or anything like that. They package the open source Apache projects with a commercial installer and bundle support and services.  The software they bundle in addition to the Apache open source is their own and is generally not open sourced.  Today they announced the latest addition to the FuseSource lineup with the Camel IDE.

Camel for those of you not familiar, “is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration. Camel lets you create the Enterprise Integration Patterns to implement routing and mediation rules in either a Java based Domain Specific Language (or Fluent API), via Spring based Xml Configuration files or via the Scala DSL. This means you get smart completion of routing rules in your IDE whether in your Java, Scala or XML editor.”

Read More of Alan Shimel’s Blog Post

Featured Blogs

Leave a Reply

(required)

(required)


ADVERTISEMENT

UC Expo

WITI

ITBriefcase Comparison Report