Skip to content

Purpose and Scope of the Document

The document outlines naming conventions and structural guidelines for organizing data domains and Kafka objects within the KaaS platform to align with business domains and enable efficient data management.

Diagrammatic Overview

Overview of KaaS Data Domains and Products

Data Domain

A Data Domain refers to a specific area or category of data that is being managed or processed. This concept aligns with the principles of Domain-Driven Design (DDD), which emphasizes structuring software projects around a business domain. In this context, a "Data Domain" can be associated with a business domain and its subdomains, aligning with the DDD approach to modeling complex software systems based on the business's specific knowledge and requirements. By identifying and defining data domains within the streaming platform, businesses can effectively align their data models with their core business processes and the various subdomains, resulting in more efficient management, processing, and analysis of data.

  • In the context of KaaS (and also for further articles in the Naming Conventions section), a Data Domain should either be a representation of a Business Domain or it should be a representation of a Business Domain and one of its subdomains.

Naming Rules

Data domain names: - Must contain only - alphanumeric characters [a-z 0-9] - (only lower case characters should be used - this is due to a technical restriction on the naming standards to be followed for the associated resources on the KaaS-AWS account) - underscores ( _ ) - no other special characters should be used - In case the data domain is composed of a Business Domain & a Sub Domain, we recommend using an underscore in between the names for readability purposes. - Example:

Data Product

A data product is a reusable data asset that bundles data together with everything needed to make it independently usable by authorized consumers. - A data domain could have one or more data products set up under it. - Data publisher/consumer should be granted access to the Kafka resources (topics, schemas, etc.) on a data product level.

Considerations

  • A data product could be named after the system of records (data source)
  • A data product name could take inspiration from the medallion architecture and could include the terminology of bronze/silver/gold in the name.

Naming Rules

Data product names: - Must contain only - alphanumeric characters [a-z 0-9] - (we recommend using only lower case characters) - underscores ( _ ) - no other special characters should be used

Examples

Generic

Below examples are not specifically taken from Novo Nordisk and have been provided for inspiration. Data Domains - finance_billing - finance_general_ledger - finance_payroll - Data Product: payroll_transactions - Data Product: employee_compensation - manufacturing_procurement - Data Product: purchase_orders - manufacturing_inventory_management - Data Product: realtime_inventory_tracking - Data Product: stock_movement_history

NN Specific

Below examples are taken from the data domains and data products currently configured on the KaaS platform. Data Domains - karen (represents the drug development business area) - master_data_products - master_data_reference_data