best-practices-for-confluent-schema-registry Blog Related Topics 
Confluent
MAY 28, 2019
Part 1 of this blog series by Gwen Shapira explained the benefits of schemas, contracts between services, and compatibility checking for schema evolution. In particular, using Confluent Schema Registry makes this really easy for developers to use schemas, and it is designed to be highly available.
Confluent
JUNE 26, 2019
This blog post discusses why Apache Kafka became the de facto standard and backbone for microservice architectures—not just replacing other traditional middleware but also building the microservices themselves using DDD and Kafka-native APIs like Kafka Streams, KSQL, and Kafka Connect. Martin Fowler. This can be answered in two parts: 1.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Confluent
SEPTEMBER 20, 2019
Luckily for on-premises scenarios, a myriad of deployment options are available, such as the Confluent Platform which can be deployed on bare metal, virtual machines, containers, etc. Before Confluent Cloud was announced , a managed service for Apache Kafka did not exist. But deployment is just the tip of the iceberg.
Confluent
AUGUST 19, 2019
It points to best practices for anyone writing Kafka Connect connectors. Recently, Confluent introduced a revised Verified Integrations Program to support the goal of supplementing connectors provided by Confluent with high-quality and well-vetted integrations from partners.
Confluent
AUGUST 14, 2019
Before Confluent Platform 5.3, Before Confluent Platform 5.3, Confluent Platform 5.3 It extends the security capabilities originally introduced in KIP-226 for brokers and KIP-297 for Kafka Connect, and provides additional functionality for encrypting the secrets across all of Confluent Platform.
Expert insights. Personalized for you.
83 
Let's personalize your content