Skip to content

Agile integration with JBoss by Red Hat

What is JBoss Fuse?

JBoss is an agile solution for API-centric, container based architecture. It combines several different open source technologies, including Apache Camel, Active MQ and many others, into one integration platform.

A fast changing world demands an integration platform that can keep up with the pace

The biggest challenges in integration we see today are not building new fresh solutions, but integrating and replacing legacy systems. One of the best examples of this are BSS systems in large enterprises such as telcos. This is especially the case with billing systems. Most of them are either too expensive or too risky to replace.

On the other hand, both companies and vendors are looking for “step-by-step” solutions with small deliverable units when it comes to replacement projects. Modern DevOps, CI/CD automation and agile methods are sending waterfall development cycles to history. Integration has to be agile, enabled for adoption, and capable to integrate with all kinds of different technologies.

Today’s integration platforms are expected to include these approaches, to be easily integrated and to support many different technologies.

With a set of integration patterns and more than 150 connectors ready to use, JBoss Fuse supports integration across the extended enterprise – including applications and services on-premise, on mobile devices, or in the cloud.

To the open source and back

We see that open source is driving more and more projects in today’s fast-moving organizations.

Its main benefit might not even be the fortunate absence of license costs, but the big community behind open source technologies. Development of these tools is not just following market needs, trends and some person’s idea for a good product, but follows the natural evolution of technologies. Many Java frameworks, such as Spring and Camel, are constantly being improved to stay aligned with current development needs.

JBoss Fuse congregates many open source projects, including Apache Camel, Apache Craft, 6F, Active MQ, and others, into one integration platform. With more than 150 adapters it ties lots of services together. This is why JBoss Fuse is loved by both entry-level developers as well as advanced Java developers, as it provides tooling for both. Above all, it is supported on OpenShift, which brings DevOps and development closer together. In short, it gives the opportunity to combine solutions in a more simple way.

Why we need JBoss by Red Hat

Many organizations are going fully open source, implementing their middleware with Camel, Spring Boot or any other programming language. And in some occasions that works like a charm. The problems however start arising when organizations begin with implementing standardized concepts in large ecosystems and big enterprises.

Camel itself offers a decent number of connectors, is very flexible when it comes to the platform, and is quite easy to maintain. The question is: is that enough? Big organizations have many regulations when it comes to security, enterprise support, risk management, etc. 

On the other hand, you would usually need a team of experts to set up and maintain a platform, establish the development guidelines, and create standards. 

With JBoss, most of the obstacles and challenges described above are either already resolved, or easily solved with little effort, without losing all the benefits of open source. 

ORGANISATIONS USING RED HAT JBOSS FUSE BENEFIT FROM:

  • Near-universal connectivity: The ability to connect all enterprise assets for consistent, efficient, and automated solutions.
  • Flexibility across an open, hybrid cloud: Deployment and management across all major cloud environments, tooling for provisioning servers, and debugging and maintaining integration services.
  • Ease of adoption: Easy, fast integration of services and applications using enterprise integration patterns and a multitude of connectors with Apache Camel.
  • Reduced maintenance costs: Selective installation of just the components you need for a small footprint.