Governance

As explained in Apache Kafka in Action

Governance is the structured oversight of data, security, and resource practices that controls how a technical system is operated and maintained.

Governance provides structured oversight for operating and maintaining Kafka-based data systems. In an e-commerce platform, it helps keep product data consistent, protect payment information, and prevent one client from overwhelming the cluster. section 13.0

Effective governance coordinates several operational concerns:

• Schema management preserves data integrity and compatibility as producers and consumers exchange evolving records. section 13.0
• Authentication, authorization, encryption, and access control protect sensitive data and restrict who can access or modify it. section 13.0 section 18.1.4
• Resource management and quotas limit resource hogging and help preserve cluster performance for other users and applications. section 13.0 section 18.1.4

Schema evolution in an online store

If a producer adds a field without coordinated schema governance, an unprepared downstream consumer may fail. Inconsistent product records can then corrupt inventory information or produce incorrect pricing. Agreed schema contracts reduce these compatibility risks. section 13.0 section 18.1.4

A data-mesh arrangement distributes responsibility. Producing business units publish data products, manage their life cycle and quality, follow schema contracts, and grant access. Consuming units request access and comply with schema and data-protection rules. The platform team supplies infrastructure and repeatable processes so teams can work without requiring central intervention for every change. section 18.1.4

Figure 18.3 Kafka in a data mesh architecture

Use the architecture figure to relate Kafka’s data-product flows to schema enforcement, access control, quotas, compliance, and decentralized departmental responsibilities. section 18.1.4

How Apache Kafka in Action covers it

How deep it goes

Explains governance responsibilities and risks through schemas, security, quotas, and data-mesh roles without implementation procedures.

Examples

Uses evolving product schemas, inventory and pricing errors, payment-data exposure, resource hogging, and departmental data products.

What you can do after

Evaluate/understand how governance assigns data, security, access, and resource responsibilities across Kafka departments.

How it connects

Connects schema management, schema contracts, authentication, authorization, encryption, access control, quotas, compliance, and data mesh.

liveBookmanning.com

Read Apache Kafka in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Authorization in ActionA governance framework is a structured system that assigns responsibility, establishes applicable standards, and coordinates work across teams or systems.
• 

  liveBookmanning.com
  Data-Driven CybersecurityThe system of leadership, oversight, decision rights, policies, and accountability through which an organization directs and controls cybersecurity.
• 

  liveBookmanning.com
  Delivering Machine Learning Projects: From design to deploymentSystem governance is the set of decision rights, controls, responsibilities, and processes that direct and oversee a system throughout its lifecycle.
• 

  liveBookmanning.com
  Prompt Engineering in PracticeThe policies and processes used to control review, maintenance, and responsible operation of an artifact or system.

Compare how 5 books explain governance →

Related concepts

• code reviewuses · Code review is the systematic examination of source code or proposed changes to identify problems and assess or improve quality.
• versioninguses · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.
• authorization decisionhas part · An authorization decision determines whether a principal is permitted to access a resource or perform an action under applicable permissions or policy.

This explainer was generated by Manning's knowledge graph from the text of Apache Kafka in Action. The section links point to the parts of the book it draws on.