Typical microservices outbox pattern implementation requires developers to manually create the outbox event table and write the codes to send the data from the outbox table to the respective messaging platform. Debezium Outbox Event Router together with Outbox Quarkus Extension take cares of this and enforce a standard approach to do this with declarative implementation. This allows the developers to focus on business logic implementation and achieve faster application delivery.
These open source tools are used by Red Hat to help their customers in digital transformation journey making the application modernization more achievable and easier compared to the past, with higher success rate.
Application modernisation is not just about the applications but also need to consider the impact of the modernising exercise to the existing internal costing and budgeting model (if any), governance processes & policies (or SDLC), the supporting services, the operation and application team, and the underlying application platform.
We all know Serverless, Function and Knative are meant to provide modern application platform for consumption based, faster start-up, lightweight, cost effective, event based, modular and etc. But how do they relates to each other and how they are different from each other. What do I need to know in order to help me to craft or choose the right solution for my organization needs.
Running ServiceMesh or Istio on OpenShift is pretty easy as long as you understand the differences between upstream community Istio and Red Hat ServiceMesh. With the enhancements tweak for OpenShift it makes managing and running microservice applications on Istio peanut easy both for administrators and developers.
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
In this article, we look at how to deploy Apache Kafka on Red Hat OpenShift 4, using reasonable sample microservice applications to showcase the endless possibility of innovation brought by OpenShift and Kafka.