My Fuse co-workers have been busy beavering away on a new project at Apache called Camel K. It’s a fantastic new project which brings together two amazing technologies: Kubernetes and Camel. Lets face it, even when your building new applications using all the new goodness that Kubernetes brings to the table, your going to need to interact with existing systems, some of which could be harder to access than others. Thats where Camel tends to shine. Giving you a consistent abstraction to accessing and integrating to those other systems.
I’m happy to announce that Red Hat Fuse 7.0 is now officially available! This is major new release which focused on expanding support for distributed hybrid integration deployments. Fuse now comes in 3 distributions:
I’m happy to announce that JBoss Fuse Integration Service 2.0 has been released. The Fuse team has been hard at work bringing Camel 2.18, Spring Boot, to the OpenShift platform. This is the best platform to develop and operate integrations in a micro microservice architecture. It lets you create tailored containerized integration applications that package only the middleware services that you need and no more.
I’m pleased to announce the availability of Apache Apollo 1.0. Apollo is a faster, more reliable, easier to maintain messaging broker built from the foundations of the Apache ActiveMQ project but with a radically different threading architecture which lets it scale to large number of concurrent connections and destinations while using a constant number of threads.
ActiveMQ Apollo is a new generation of messaging broker built from the foundations of the ActiveMQ messaging broker, but using a radically different threading and message dispatching architecture. In it’s current incarnation, Apollo only supports the STOMP protocol but just like the original ActiveMQ, it’s been designed to be a multi protocol broker and in future iterations it should get OpenWire support so it can be compatible with ActiveMQ 5.x JMS clients.