A True Atomic Microservices Implementation with Debezium to Ensure Data Consistency

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.

What Are The Differences Between Function, Serverless and Knative?

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.

Uniform Way to Connect, Secure and Monitor Microservice Applications with Red Hat ServiceMesh

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.

Implementing Integration Service with Apache Camel

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.