Skip to content

Registry Naming Conventions

DNS Classification

A registry name consists of multiple components, which can be categorized into two types: service names and application names. Each component has a specific meaning that helps identify the function, environment, and ownership of the service or application.

Service Names

Note

This is used mainly for EXTERNAL connection

Example: qcnex-qcint.quintessence.de

  • qc – Designates the service environment.
  • nex – Represents the application name.
  • qcint – Indicates that the service belongs to the Quintessence internal environment.

Application Names

Note

This is used mainly for EXTERNAL connection

Example: mgewdev-qcint.quintessence.de

  • mg – Represents the application.
  • ew – Identifies the customer.
  • dev – Specifies the classification (e.g., development environment).
  • qcint – Indicates that the application belongs to the Quintessence internal environment.

This structured naming convention ensures clarity and consistency across different services and applications within the Quintessence infrastructure. 🚀

Internal Network Connection

Note

This is only for INTERNAL connection

If you need to use an internal connection, for example, between APPs like ASGARD and Midgard on port 8080, you should use the short name of the virtual machine (VM) within the internal network.

Example: 

mgewdev:8080
asgewdev:8080

Reasons:

  1. Reduced DNS Load – Using a short name avoids unnecessary DNS resolution, speeding up the connection.
  2. Optimized Routing – Internal names allow data to be transmitted within the network without external routing.
  3. Simplified Configuration – Internal services can communicate without reliance on domain names, reducing deployment complexity.
  4. Enhanced Security – Internal connections do not require external access, minimizing security risks.

Naming Logic:

  • The VM short name (mgewdev) follows the internal naming convention, where:
    • mg represents the application.
    • ew identifies the customer.
    • dev specifies that this is a development environment.
  • The port number (8080) is specified because applications often expose their services on specific ports. Including the port ensures the connection reaches the correct service running on the VM.

Thus, for service-to-service communication within the internal network, it is recommended to always use short VM names along with the appropriate port to ensure efficient, secure, and direct communication between services. 🚀

Changelog

Date Author Message
2026-02-25 aresnikowa Merge remote-tracking branch 'origin/master'