Featured Posts
- Debezium Operator Takes off to the Clouds
- Debezium signaling and notifications - Part 3: JMX channel
- Online machine learning with the data streams from the database
- Debezium signaling and notifications - Part 2: Customisation
- Debezium signaling and notifications - Part 1
- Image classification with Debezium and TensorFlow
- Streaming Vitess at Bolt
- Distributed Data for Microservices — Event Sourcing vs. Change Data Capture
- Building Audit Logs with Change Data Capture and Stream Processing
- Streaming Cassandra at WePay - Part 1
- Reliable Microservices Data Exchange With the Outbox Pattern
- Automating Cache Invalidation With Change Data Capture
- Materializing Aggregate Views With Hibernate and Debezium
- Five Advantages of Log-Based Change Data Capture
- Creating DDD aggregates with Debezium and Kafka Streams
- Streaming Data Changes from Your Database to Elasticsearch
Tags
apache kafka apache kafka apicurio avro aws caassandra camel cassandra cdc channels community community stories containers cqrs custom datalake db2 ddd debezium debezium server debezium ui deduplication discussion docker elasticsearch event sourcing exactly once semantics example examples features fedora flink hiring iceberg informix integration introduction jaeger json kafka kafka streams kafka streams kogito ksql kubernetes lakehouse machine learning mariadb microservices mongo mongodb mysql news newsletter notifications online learning operator oracle outbox postgres presentation production quarkus questdb rds releases schema scylla secrets sentry serialization signaling smt snapshots spanner spark sql sqlserver tensorflow testcontainers tests time series topics tracing transactions vagrant vitess website
Debezium Blog
When a Debezium connector is deployed to a Kafka Connect instance it is sometimes necessary to keep database credentials hidden from other users of the Connect API.
Let’s remind how a connector registration request looks like for the MySQL Debezium connector:
