The rapid deployment of next-generation communication networks is fundamentally changing the requirements for corporate IT architecture. According to the Ericsson Mobility Report November 2025, the number of 5G connections worldwide is growing rapidly and is projected to reach 6.4 billion by the end of 2031. Against this backdrop, over 90 service providers have already launched or are preparing for the full-scale launch of commercial 5G Standalone (SA) networks. For businesses, this means an exponential increase in the volume of data generated by industrial IoT devices, telemetry systems, and mobile platforms.
The main challenge is that the traditional approach to the cloud as a static set of virtual servers no longer works. To maintain low latency and high throughput, organizations must transition from reactive capacity expansion to dynamic, managed cloud environments with strict cost and security controls at the architectural level.
The scaling trap: why static cloud cannot handle IoT dynamics
Many companies attempt to solve the problem of growing traffic by simply allocating additional resources in public or hybrid clouds. However, an architecture designed for static workloads proves ineffective under the pressure of dynamic 5G data flows. The primary mistake lies in perceiving infrastructure as an immutable resource rather than a continuous lifecycle.
Monolithic systems or poorly optimized microservices are unable to adapt instantly to peak loads. During periods of high network activity, the infrastructure becomes overloaded, while during downtime, the organization continues to pay for unused computing power. Migration to the cloud alone does not solve financial problems; without clear design and automation, it merely converts capital expenditures into uncontrolled operational ones.
The anatomy of chaos: cloud sprawl and vulnerabilities at the intersection of technologies
Uncontrolled cloud sprawl and the emergence of vulnerabilities are consequences of chaotic scaling. Architects most often face three critical problems:
- Over-provisioning without auto-scaling. Deploying IoT data ingestion layers without configuring flexible auto-scaling policies leads to virtual machines or containers remaining idle most of the time.
- Ignoring the security of legacy protocols. When integrating cloud platforms with telecom networks, the need to support hybrid environments arises. Often, insufficient attention is paid to the security of legacy signaling protocols such as SS7 or Diameter. This creates entry points for attackers. 5G technology is not a source of threat in itself—risks arise due to infrastructure design errors and the use of outdated interfaces.
- Lack of cost attribution. Due to the absence of a standardized resource tagging system, IT departments cannot track which business units or microservices consume the most budget, making precise financial planning (right-sizing) impossible.
FinOps: cost optimization at the architectural design stage
The FinOps concept should be implemented not as a one-time audit of invoices, but as a continuous operational model. According to the Microsoft Azure Well-Architected methodology, design-stage cost modeling is significantly more effective and practical than attempting to optimize infrastructure after deployment.
The first step is to implement a strict tagging policy for every cloud resource. Each container or network gateway must have labels indicating the owner, project, and environment. The next step is dynamic management: using serverless architecture and clusters with horizontal auto-scaling allows organizations to pay only for actual data processing operations performed.
Security-by-Design and NIS2: protecting critical access points
According to the ENISA Threat Landscape 2025 report, essential entities under the NIS2 Directive accounted for a significant portion of all recorded security incidents. This indicates that regulatory requirements for infrastructure resilience are becoming increasingly stringent.
To ensure readiness for modern threats, Cisco, in its Cybersecurity Readiness Index 2025, identifies five key pillars of security: Identity Intelligence, Machine Trustworthiness, Network Resilience, Cloud Reinforcement, and AI Fortification.
Implementing these requirements in hybrid clouds involves isolating signaling traffic from general resources through micro-segmentation and adopting a Zero Trust architecture, where every API request is subject to strict authentication.
Practical transition and technological foundation
For the successful scaling of mission-critical solutions, companies require proven architectural patterns. Within the Intecracy Group alliance, which consists of independent companies linked by partner agreements and share exchanges, expertise in custom software development, AI integration, and outsourcing is provided by Softengi. The company's specialists, certified under the ISO/IEC 42001:2023 AI management standard, help design architectures that prevent uncontrolled cloud resource sprawl.
The technological foundation for many enterprise systems is the UnityBase platform—a full-stack JavaScript low-code framework. Using Domain metadata mechanisms for automatic REST API generation and database structure synchronization reduces the risk of architectural errors during the integration of cloud and on-premises systems.
To ensure compliance with security standards, particularly NIS2 requirements, UnityBase provides necessary access control mechanisms in its commercial Enterprise and Defence editions: a role-based model (RBAC), row-level security (RLS), access control lists (ACL), detailed user action audit trails, and support for modern authentication protocols (e.g., OpenID Connect/OAuth2). This forms a reliable foundation for load-resistant data management systems.
Checklist for 5G/IoT infrastructure scaling readiness
- Mandatory tagging of all cloud resources implemented for accurate project-based cost attribution.
- Auto-scaling policies configured for IoT data ingestion layers to avoid paying for idle time.
- Audit and isolation of legacy signaling protocols (SS7/Diameter) conducted in the hybrid environment.
- Cost estimation model implemented at the design stage (in accordance with Azure Well-Architected principles).
- Architecture meets NIS2 requirements regarding network resilience and protection of critical objects.
FAQ
How can unpredictable costs be avoided when deploying IoT platforms in the cloud?
It is necessary to implement design-stage cost modeling, configure mandatory resource tagging for cost attribution, and use auto-scaling policies to adapt capacity to actual loads.
Which security requirements are critical for cloud infrastructure in the context of NIS2?
Critical factors include ensuring Network Resilience, implementing the Zero Trust concept, isolating legacy signaling protocols from general computing resources, and ensuring continuous auditing of user actions.
Why do traditional monitoring methods fail to prevent cloud sprawl during scaling?
Traditional monitoring focuses primarily on server health but does not link resource consumption to specific business processes. To eliminate cloud sprawl, a continuous FinOps model with tagging and automated shutdown of unused environments is required.