Skip to content
braindose.blog
Menu
  • Home
  • Open Source
    • .Net
    • Apache Camel
    • Apache Kafka
    • APIs
    • Containers
    • Data Services
    • Development
    • DevOps
    • Kubernetes
    • Microservices
    • Monitoring
    • Openshift
    • Quarkus
    • Serverless
    • ServiceMesh
    • Workflow & Business Rules
  • Raspberry Pi
  • Series
    • Event-Driven Payment
    • Payment
    • K8s on RPI4
  • Solution
    • Application Modernization
  • Others
  • About
Menu

Category: Apache Camel

Debezium CDC with Camel Connector

Debezium Change Data Capture without Apache Kafka Cluster

Posted on December 8, 2022August 11, 2023 by CK Gan
0
0
0
0
0
0
0
0
0

Debezium is developed base on Kafka Connect framework and we need Apache Kafka cluster to store the captured events data from source databases. Sometime we do not require the level of tolerance and reliability provided by Apache Kafka cluster, but you still need Change Data Capture (CDC). This is where Debezium Engine come into the picture.

Read more

Event-Driven Payment Exceptions Handling Using Kogito

Posted on November 15, 2021December 29, 2021 by CK Gan
0
0
0
0
0
1
0
1
0

Let’s go through in detail how can we use the Kogito services to help us to modernise the payment platform by following the event-driven architecture approach. Kogito is the right fit in the scenarios where you need to implement decision services and business automation for an event driven architecture, with the fact that it is purposely built for events and cloud-native use cases.

Read more

Implementing Integration Service with Apache Camel

Posted on June 5, 2020December 29, 2021 by CK Gan
0
0
0
0
0
0
0
0
0

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.

Read more

Follow us on Social Media
x youtube linkedin github

Recent Posts

  • Debezium Change Data Capture without Apache Kafka Cluster

    Debezium Change Data Capture without Apache Kafka Cluster

  • Kubernetes Disaster Recovery

    Kubernetes Disaster Recovery

  • Monitor and Analyze Nginx Ingress Controller Logs on Kubernetes using ElasticSearch and Kibana

    Monitor and Analyze Nginx Ingress Controller Logs on Kubernetes using ElasticSearch and Kibana

  • Running ElasticSearch and Kibana on RPi4 for Logs Analytics

    Running ElasticSearch and Kibana on RPi4 for Logs Analytics

  • Automate Kubernetes etcd Data Backup

    Automate Kubernetes etcd Data Backup

Archives

AMQ Streams apache camel Apache Kafka Apache Kafka Connect Apoche Kafka Connect application modernization business automation Business Rules CDC CI/CD Container Debezium decision service Docker elastic elasticsearch Event Processing fluentd GraalVM integration Jenkins kibana knative kubernetes logs microservices MongoDB OpenShift payment payment modernization quarkus raspberry pi red hat Red Hat Fuse serverless ServiceMesh springboot synology ubuntu uncluttered email uncluttered inbox wfh work from home work life balance work remotely

©2021 braindose.blog

a little dose to light up your days