On the need to merge architectural and infrastructural considerations

This work takes the position that attempting to keep a separation between the logical and deployment view of modern, cloud-native software systems only leads to a new type of technical debt that manifests during the operational side of the lifecycle. This is an issue that is fueled by the treatment of software qualities without considering where the systems under consideration are supposed to be deployed, and how long it takes until positive or negative treatments on these qualities manifest themselves. Sustainability is a particularly interesting case of a quality that requires logical and deployments views to be taken into account in a unified way.