Software Defined Everything ‐
Architectural Principles and Automation
Software Defined Everything
Software-Defined Everything (SDx) describes an architectural approach in which technical resources and functions are largely abstracted from their specific hardware implementation and are controlled, configured and managed via software. In this approach, functionalities are no longer determined exclusively by the properties and configuration of the underlying hardware, but can be defined, controlled and further developed via software. SDx thus creates programmatically accessible building blocks that can be provided and managed via defined, preferably standardized interfaces. This abstraction reduces dependence on specific hardware implementations and enables flexible, software-controlled use and further development of the underlying technical resources and functions. SDx should not be understood as a uniformly standardized architectural model, but rather as an overarching principle that is implemented differently depending on the technological domain.
One concrete manifestation of this approach is the Software-Defined Data Center (SDDC). In this model, the traditional infrastructure domains of compute, storage, and networking are abstracted using software-defined technologies and made available as flexible resources. The terms Software-Defined Compute (SDC), Software-Defined Storage (SDS), and Software-Defined Networking (SDN) describe the functional domains within an SDDC.
VMware Cloud Foundation (VCF) illustrates this approach through the integration of its software-defined infrastructure components. VMware vSphere handles the virtualization and provisioning of compute resources (SDC). VMware vSAN enables the software-based provisioning and management of storage resources (SDS), while VMware NSX enables the virtualization and software-based control of the network infrastructure (SDN).
IT Automation
IT automation refers to the ability to combine, configure and operate IT resources - including software-defined resources - and functions through defined rules, workflows, interfaces and events. Technologies and concepts such as Infrastructure as Code (IaC), automated provisioning, configuration management and orchestration make it possible to deploy infrastructure components and applications with minimal recurring manual intervention and to manage them throughout their entire lifecycle.
Application Programming Interfaces (APIs) and declarative configuration models forms the key technical foundation for this. They make it possible to access the functions and resources of software-defined infrastructures via defined interfaces, describe desired states and initiate changes programmatically. Automation platforms leverage these capabilities to provision resources, adjust configurations and control cross-system processes.
One example of this is VCF Automation. The software-defined infrastructure components forms the technological foundation on which resources can be provisioned and consumed via defined services and interfaces, self-service functions and automation workflows. With concepts and features such as IaC, blueprints, and policy-based governance, software-defined infrastructure is made available as an IT service that can be used as needed.
Red Hat Ansible offers a complementary perspective. With Ansible process automation tasks can be described in playbooks and implemented in a reusable manner. Modules enable the execution of specific automation tasks. Collections bundle reusable automation content, while roles support their structuring and reuse. The range of applications extends from configuring operating systems and network components to installing software and deploying applications, all the way to provisioning and managing infrastructure resources. With the Ansible Automation Platform (AAP) this automation content can be executed centrally and orchestrated through workflows. Event-Driven Ansible makes it possible to respond to defined events from the IT infrastructure and trigger automated actions based on them.
While VCF Automation focuses specifically on the provisioning and self-service consumption of software-defined infrastructure resources, Ansible extends automation to include configuration, integration and operational processes across different IT domains. Both approaches can complement each other and, together, help automate not only the initial provisioning but also the configuration, integration, and continuous adaptation of IT services throughout their entire lifecycle.
Interplay Between SDx and IT Automation
SDx and IT automation constitute two closely interrelated aspects of modern IT architecture:
While SDx provides programmatically accessible infrastructure components and their software-based control, IT process automation enables their standardized, repeatable and cross-domain use. APIs, declarative models and automation workflows forms the technical link between these two approaches. This allows software-defined infrastructures to be efficiently transformed into consumable IT services. The more systems are defined by software, the more important automation becomes.
SDx - a Cross-Industry Architectural Principle
Beyond traditional IT infrastructure, the software-defined principle can also be found in other technological domains. Examples include mobility with the Software-Defined Vehicle (SDV) and the defense sector with Software-Defined Defense (SDD).
While the technical implementations sometimes differ significantly, the underlying architectural principles share commonalities. These include, in particular, the abstraction and modularization of technical functions, the decoupling of hardware and software, the provision of defined interfaces and the ability to control and further develop systems via software throughout their entire lifecycle.
These are architectural analogies and functional similarities, not direct equivalences between individual technologies or components. For example, SDC cannot be directly equated with a specific vehicle computer, even though both perform comparable tasks with regard to the provision and processing of computing power.
Software-Defined Defense (SDD) occupies a special position. It is less a single technical platform or infrastructure domain and more of an overarching paradigm for the software-based digitization, networking and continuous development of military systems and capabilities.
Domain-Specific Manifestations of SDx Architecture Principles
SDDC, SDV, and SDD follow similar architectural principles but differ significantly in terms of the system under consideration, their technical implementation and the requirements for their operation. They represent three different application areas of the same overarching architectural concept.
SDDC Principles
The Software-Defined Data Center describes the software-defined architecture of an IT infrastructure and is based on the abstraction and software-based provisioning of compute, storage and network resources. The goal is a flexible, scalable and automatable IT infrastructure. It thus forms an integrated infrastructure platform that can be programmatically managed and utilized via APIs and automation mechanisms. A key characteristic is the decoupling of infrastructure resources from their physical implementation, as well as their provisioning as flexibly usable services.
SDV Principles
The Software-Defined Vehicle describes the software-defined architecture of a vehicle and takes the approach of increasingly decoupling vehicle functions from their specific hardware implementations. The goal is a vehicle whose functions can be further developed, updated and expanded via software. This shifts the focus from a multitude of functionally distinct electronic control units to a more integrated vehicle architecture with centralized, domain-oriented computing platforms. A key characteristic is that vehicle functions are increasingly defined by modular software and can be further developed throughout the vehicle's entire lifecycle.
SDD Principles
Software-Defined Defense (SDD) refers to an overarching architectural and transformation-oriented approach that aims to modularize, network and further develop military systems and capabilities through software. SDD encompasses not only technological and architectural aspects but also requirements related to governance, standardization and procurement processes. The goal is to achieve greater adaptability and interoperability throughout the entire system lifecycle. It is therefore characterized not by a single technical architecture, infrastructure or platform, but by the software-based evolution and integration of military capabilities across different systems and domains. Overall, SDD pursues a more comprehensive transformation approach. The integration and updating of such systems are subject to stringent requirements for interoperability, information security, validation and controlled release.
Common Architectural Principles
This comparison illustrates that the common foundation of these architectural approaches lies in the abstraction, modularization and software-based controllability of technical functions. However, their specific implementation is largely determined by the respective domains.
Automation as an Operational Enabler for Software-Defined Products and Capabilities
As technical systems become increasingly software-defined, the importance of automation is also growing. It is no longer limited exclusively to the provision and configuration of technical resources, but increasingly encompasses the development, integration, validation and deployment of software-defined systems, as well as their continuous improvement throughout their entire lifecycle.
In the SDV context, the focus is on an end-to-end automation chain that spans from software development through integration and validation to the deployment and updating of the vehicle fleet. Automation becomes an essential component of product development and product operation. Vehicle functions are no longer determined solely by the factory-default settings but can be further developed and expanded throughout the vehicle's entire lifecycle, within the technical and safety-related parameters.
In SDD this perspective goes beyond the further development of individual software components. Here the focus is particularly on integrating new software-based capabilities into existing military systems and platforms. Automated development, integration, validation and deployment processes support the controlled further development of these capabilities.
A connection to the automation technologies discussed earlier - VCF Automation and Ansible - emerges at the level of the supporting IT and development infrastructure. For example, both can automatically provision, configure and operate the cloud infrastructure of an SDV software factory or the IT platform of an SDD development environment. They support the underlying development, integration and test environments; however, they do not automatically take over the control of safety-critical vehicle functions or the mission-related runtime management of military systems.
This demonstrates that infrastructure automation remains an important foundation in the SDV and SDD context, but constitutes only one part of a more comprehensive automation architecture. Only through interaction with domain-specific development, integration, validation and deployment processes can end-to-end automation of the product and system lifecycle be achieved.
Conclusion
Software Defined Everything describes a cross-industry architectural principle that focuses on the abstraction, modularization, and software-based control of technical systems. An exploration of SDDC, SDV and SDD illustrates that these principles are applied in various technological domains, although their specific implementation is determined by the respective domain-specific requirements.
The increasing software-definition of technical systems is simultaneously changing the requirements for their automation. While the provision and management of infrastructure resources take center stage in the traditional IT environment, automated development, integration, validation and continuous improvement are gaining importance in the context of software-defined products and capabilities.
In this context, two closely related levels of automation can be distinguished:
- Infrastructure Automation and Process Automation includes the automation of the technical platform on which development, integration and operation take place.
- Software Lifecycle Automation focuses on the automation of product and system development, as well as their integration, validation, deployment and continuous improvement.
Both levels complement each other and together form the foundation for an end-to-end automation architecture. This makes automation an essential component of modern software-defined architectures throughout their entire product and system lifecycle.