Skip to content

Purpose and Scope of the Document

This document serves to provide comprehensive answers to frequently asked questions (FAQs) regarding events, data/event streaming, and the Kafka-as-a-Service (KaaS) platform at Novo Nordisk.

Q1. What are events?

Events represent meaningful actions or occurrences captured by your system and stored for further processing or analysis. An event is a record of an action or occurrence, whether generated by a user or triggered by software. They serve as indicators of operations within your system, such as creating, updating, or deleting resources.

Examples:

  • Manufacturing Process Monitoring:
    Streaming events can capture sensor measurements from equipment during drug production. These events might include temperature, humidity, or pressure readings that ensure production stays within safe and regulated parameters. By streaming these measurements, manufacturers can detect anomalies in real time and make process adjustments to maintain quality and compliance.
  • Clinical Trial Data Collection:
    In clinical trials, real-time streaming can capture numerous digital records. For instance, events such as patient lab test results, response times to experimental drugs, or even medication adherence records can be streamed. This continuous flow of data helps research teams monitor trial progress, rapidly identify adverse reactions, and adjust protocols based on emerging trends.

Q2. What is Data/Event Streaming?

Data/event streaming involves processing a continuous flow of information in real time. It focuses on capturing, storing, processing, and reacting to events as they occur or after the fact. It enables real-time monitoring, analytics, and automated responses across various applications.

Q3. What are some of the use cases relevant in NN?

  • Real-Time Manufacturing Monitoring: Track production metrics in real time for quality checks and optimizations.
  • Supply Chain Visibility: Stream events from logistics and inventory systems for transparency in monitoring storage conditions and shipments.
  • Regulatory Compliance and Audit Trails: Maintain durable logs of operational data for compliance with industry regulations.
  • IoT Data Integration from Lab Instruments: Ingest and process telemetry data for real-time analysis.
  • Data Integration Across Decoupled Systems: Integrate data from clinical trials, research outcomes, and operational systems.

Q4. What is KaaS and is it GxP qualified?

KaaS (Kafka-as-a-Service) is a managed messaging platform built on Apache Kafka. It is GxP qualified, which means it meets necessary compliance standards and helps process data quickly while connecting systems together.

Q5. How to get quick access to Kafka for POCs and preliminary investigations?

Refer to the Playground-Setup page.

Q6. What is the cost model associated with the KaaS platform?

Read more about it here.

Q7. How does KaaS ensure data security?

KaaS employs a range of security practices to ensure data security, including:

  • Service Accounts: Service accounts are created centrally and are used to generate and own API keys. This prevents the issues associated with user-generated keys that can become invalid when a user leaves the organization.
  • Access Control: The requested service accounts and permissions are approved by the Data Domain/Data Product Owner or a delegate to grant access to critical or sensitive data safely.
  • Long-Term Vision for Security: The platform aims to adopt OAuth 2.0 and OpenID Connect for better security management, which will reduce the risk of credential theft and enhance the management of permissions, although this setup is still pending further development.
  • Standardized Roles: Users have predefined roles linked to entitlements that facilitate streamlined access management via NovoAccess, enhancing both security and usability.

Currently, KaaS supports user SSO with SAML and utilizes service accounts with API keys for system-to-system access.

Q8. What is difference between Private Cluster and Public Cluster?

The key differences between public and private Kafka clusters on the KaaS platform relate to network accessibility, connectivity and use cases:

Private Clusters:

  • Connect to the Novo Nordisk corporate network via AWS Transit Gateway.
  • Require VPN or ZScaler Private Access (ZPA) connection to access from your device.
  • Network traffic stays within private networks.
  • More secure and isolated from the public internet.
  • Typically used for Production environments, Sensitive data handling, Enterprise applications. requiring enhanced security, Strictly Confidential Information (SCI) workloads.

Public Clusters:

  • Accessible directly over the internet.
  • Do not require VPN or corporate network connection.
  • Can be accessed from any location with internet connectivity.
  • Typically used for Development and testing, Non-sensitive data, Applications that need broader accessibility, Proofs of concept (POCs).

Q9. Do we support custom connectors?

Yes, we support custom connectors. It requires additional configuration. For more details connect with Platform teams.

Not currently. We are working on it. For more information and timelines please connect with the Platform Team.

Q11. Any issues? What is the first step and whom to contact?

Q12. Any teams channel for support?

Q13. Any email to contact the KaaS platform team?

"INTC4E" INTC4E@novonordisk.com