Red Hat Fuse is base on Apache Camel, an open source project to allow developers to implement integration services quickly and easily. This article and the demo asset demonstrate one possible way of how to implement the integration service using Red Hat Fuse. With the enriched list of technology and components brought by Camel, you may find a different way to implement the same solution. This is where the EIP (Enterprise Integration Pattern) is in placed to ensure however the developer is implementing the integration, it will be ensured the developers are following the best practices outlined by the EIP. With the nature and flexibility of Camel integration approaches, we also see how easy it is for us to implement endpoints integration, message marshalling and unmarshalling, and most importantly how we can embrace reusability allowing us to bring our solution to market faster.
Let’s walk through a quick tutorial of how to migrate a simple SpringBoot application to Quarkus
Let us walk through how we failed to build the Jenkins JNPL Slave container for GraalVM with Docker and GraalVM with Podman.
In the journey of Quarkus project implementation you will need to consider what is the CI/CD process. The very first come into the picture is how to implement the CI part. We need the Jenkins JNLP slave container for GraalVM to build the Quarkus native runnable
GitOps created many buzz today and we have seen communities are starting to take a serious look into GitOps. There are many imperatives of GitOps. I have shortlisted them into four key characteristics in order to implement a successful GitOps.