resource-management-with-confluent-for-kubernetes Blog Related Topics 
Confluent
JUNE 12, 2019
Confluent Cloud, a fully managed event cloud-native streaming service that extends the value of Apache Kafka ® , is simple, resilient, secure, and performant, allowing you to focus on what is important—building contextual event-driven applications, not infrastructure. Helm Chart configuration for Confluent Cloud.
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. Microservices. 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
JULY 31, 2019
Delivers the new Confluent Operator for cloud-native automation on Kubernetes, a redesigned Confluent Control Center user interface to simplify how you manage event streams, and a preview of Role-Based Access Control for enterprise-grade security. To solve these challenges, Confluent Platform 5.3
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. To simplify all of this, different providers have emerged to offer Apache Kafka as a managed service. But deployment is just the tip of the iceberg.
Confluent
SEPTEMBER 24, 2019
Kafka clients—specifically the Kafka consumer, Kafka Connect, and Kafka Streams, which are the focus in this post—have used a sophisticated, paradigmatic way of balancing resources since the very beginning. Defining an embedded protocol within Kafka’s group management API does not restrict its use to load balancing only.
Confluent
FEBRUARY 13, 2019
We’ve quickly learned through microservices and SOA with the traditional model that RPC-based systems don’t scale, and managing state and correctness also doesn’t scale. Inactive actors are persisted to disk to minimize idle resource requirements. Do I need to use a microservices framework? Control: Offline and rolling restart.
Confluent
SEPTEMBER 13, 2019
A Kafka rebalance is a distributed protocol for client-side applications to process a common set of resources in a dynamic group. Two primary goals for this protocol are: Group resource assignment. Strictly speaking, only built-in rebalance assignors obey this rule for resource isolation. Membership change capture.
Expert insights. Personalized for you.
93 
Let's personalize your content