The launch of next-generation (5G) networks and the exponential growth of connected IoT devices are fundamentally changing the requirements for cloud infrastructure. When data volumes grow unpredictably and the number of transactions per second increases by orders of magnitude, traditional scaling approaches cease to be effective. Previously, engineers solved peak load problems by simply allocating additional capacity (over-provisioning). Today, this practice leads to uncontrolled costs and creates new cyber threat vectors, necessitating a transition to systematic architectural control.
Why traditional cloud scaling fails under 5G and IoT pressure
The main challenge is cloud sprawl—the proliferation of cloud resources where virtual machines, storage, and network gateways are created chaotically to solve immediate tasks but are subsequently left unmonitored. This not only increases cloud provider bills disproportionately to business results but also creates critical security gaps due to the lack of a unified access policy.
According to the ENISA Threat Landscape 2025 report, digital infrastructure and services accounted for approximately 27.7% of all data breaches between July 2024 and June 2025. This confirms that rapid scaling without an integrated security strategy makes infrastructure vulnerable to external threats, turning every new endpoint into a potential risk.
FinOps as a countermeasure to cloud sprawl: transitioning to controlled unit economics
To stop chaotic cost growth, engineering teams must move from reactive administration to the FinOps methodology. This is a culture of shared financial responsibility between engineering departments and the business. According to FinOps Foundation standards, cost management is a continuous cycle consisting of three phases: Inform, Optimize, and Operate.
In the context of 5G and IoT, it is critical to analyze cloud unit economics—understanding the cost of maintaining a single active IoT node or communication session. Implementing FinOps does not provide immediate cost reduction without deep process changes; it creates the transparency necessary for making architectural decisions.
Microsoft's recommendations within the Azure Well-Architected framework for Cost Optimization clearly state that modeling costs at the cloud infrastructure design stage is significantly more effective than attempting to optimize already deployed resources. Practical steps to begin optimization include:
- Automatically shutting down test environments or inactive IoT nodes outside of business hours to avoid "sleeping" costs.
- Implementing strict resource tagging policies to attribute costs to specific 5G services or business units.
- Continuous analysis of whether allocated capacity matches actual needs, rather than reserving redundant resources.
Security-by-design: protecting scalable infrastructure in the NIS2 era
Scaling communication networks expands the attack vector. In current realities, with regulatory requirements such as the NIS2 directive and the ISO/IEC 27001 standard in effect, security must be designed as an integral part of the infrastructure (security-by-design) rather than added before release.
No architecture can guarantee absolute protection against cyber threats, but risks can be significantly minimized. The Cisco Cybersecurity Readiness Index 2025, based on a survey of 8,000 cybersecurity executives across 30 countries, emphasizes the need for a comprehensive approach to security through five key pillars: Identity, Trust, Network, Cloud, and AI. When scaling infrastructure, one cannot rely solely on perimeter defense—it is necessary to implement the Zero Trust concept.
An effective tool is the use of monitoring to detect traffic anomalies that indicate the compromise of IoT devices. For example, if a node suddenly changes its data transmission pattern, the system should automatically isolate it at the network segment level until the situation is resolved.
Architectural foundation: the role of the UnityBase platform in ensuring stability
Building mission-critical systems that process data streams requires a reliable software foundation. Creating an infrastructure backend from scratch often leads to monoliths and vulnerabilities. It is more effective to use ready-made platform solutions such as UnityBase—a full-stack JavaScript low-code framework, which is a joint development of companies within the Intecracy Group alliance (an alliance of independent companies linked by partner agreements and share exchanges, not a single company or holding, where InBase acts as a key, but not the only, developer).
UnityBase uses the Domain metadata concept, where domain metadata serves as a unified model for data, user interface, API, and system behavior. This allows for the automatic generation of REST API and ensures stable integration with external databases and cloud storage while maintaining control over every transaction.
For high-load systems or projects with increased security requirements, the official UnityBase documentation recommends commercial Enterprise or Defence editions, which provide:
- Flexible access control at the row level (RLS), attribute level, and the use of access control lists (ACL).
- Built-in immutable user action audit trail, which is critical for compliance with NIS2 and ISO/IEC 27001 requirements.
- Advanced authentication mechanisms, including OpenID Connect, OAuth2, and Kerberos.
Although UnityBase does not directly process 5G telecommunication protocols, the platform serves as a reliable core for access management, business logic, and accounting. Combined with Softengi's expertise in developing specialized IoT solutions, using UnityBase allows for the construction of scalable architectures with predictable operating economics.
How to build managed infrastructure: from chaos to system design
Transitioning to systematic scaling is a continuous process. To assess the maturity of their own infrastructure, companies should use the scale below, which reflects the integration of financial control and security into the architecture.
| Maturity Level | Financial Control (FinOps) | Security Status |
|---|---|---|
| Level 1: Reactive | Chaotic scaling in response to load peaks, no cost tagging. | Security as an afterthought, reaction to incidents after they occur. |
| Level 2: Controlled | Basic monitoring implemented, resource tagging policies, regular cost audits. | Basic perimeter defense, fragmented implementation of access policies. |
| Level 3: Optimized | FinOps discipline integrated into processes, automatic shutdown of inactive IoT nodes, cost forecasting. | Implementation of the Zero Trust concept, automatic traffic anomaly detection. |
| Level 4: Strategic | Cost modeling at the design stage (unit economics), full transparency of responsibility distribution. | Security-by-design at the architectural level, NIS2 compliance, use of platforms (e.g., UnityBase) for mission-critical system stability. |
FAQ
How can uncontrolled cloud cost growth be prevented when deploying IoT networks?
It is necessary to implement the FinOps methodology, configure cloud resource tagging policies for cost attribution, and automate the shutdown of inactive nodes. The highest efficiency is achieved by modeling costs at the architectural design stage.
Which NIS2 and ISO/IEC 27001 requirements are critical for cloud communication infrastructure?
It is critical to implement the security-by-design principle, ensure an immutable audit trail, enforce strict access control (RBAC/RLS/ACL), monitor traffic for anomalies, and transition to a Zero Trust model.
How does the UnityBase platform help optimize the architecture of high-load systems?
UnityBase uses a unified Domain metadata model for automatic REST API generation and database integration. Commercial editions (Enterprise/Defence) provide built-in access control (RLS, ACL) and audit mechanisms, which accelerate the development of secure mission-critical systems.