End-to-End-Blaupausen
Eine Bestandsaufnahme der Business Services und ihrer Cloud-Anforderungen mit Definitionen für technische Services für digitale Zwillinge.
Mit End-to-End-Blueprints kann die Erstellung eines Inventars von Business Services und den damit assoziierten Cloud- und Plattformservices einfach generiert werden.
Durch die Identifizierung von Gemeinsamkeiten und die Definition von Gruppierungen technischer Dienstleistungen kann ein digitaler Zwilling jedes Geschäfts Buchungen bearbeiten unter Verwendung eines Cloud-Edge-Kontinuums gebildet werden. Die benötigten Oberflächen werden durch ein Netzwerkdesign geschaffen, das die Vernetzung der einzelnen technischen Dienste im Cloud-Edge-Kontinuum darstellt. Dies ermöglicht die automatische Erstellung und Verwaltung von Verbindungsdefinitionen innerhalb des Cloud-Edge-Kontinuums aus dem Netzwerkentwurf heraus.
Komponenten
Like functional data, the individual and overall blueprints required for automation must be synchronized bi-directionally between the main and DR site.
This synchronization between main & DR site must be automated and reliable with as little delay as possible for a successful switchover.
This is central to achieve low RPO values, especially for critical services.
Blueprints are the fundamental concept by which services are described. They include a functional end-to-end description of each service, its configuration & dependencies.
The functional abstraction from the infrastructure enables deployment of the services in different locations with different hardware, regardless of the vendor.
Blueprints are arranged in a hierarchical structure to obtain an overall functional blueprint for a data centre.
For each level of the hierarchy, the definition of the blueprint structure also contains the corresponding execution layer.
Description of language interfaces and APIs for connection management with generation of network blueprints and an execution layer for network blueprints.
Develop a functional connection description that does not depend on the underlying infrastructure.
Service providers then only describe the characteristics of their services (protocol, port, etc.)
Client services describe the desired functional connections (e.g. from application X to database Y).
Automatic and dynamic creation of a new network blueprint for all intermediate network components including the network topology data from the sum of all these descriptions.
Automated generation of all basic components
Creation and configuration of the basic infrastructure components such as landing zones, data storage, container platforms, etc. as well as the middleware and tools (e.g. monitoring) that are used by the various blueprints.
In addition to deployment, this also includes maintenance of these components, such as the automatic distribution of updates and patches.