Topic starter
09/07/2026 3:25 pm
TL;DR: As data volumes grow, legacy, vertically scaled architectures create bottlenecks, with read-heavy Command Center calls taking 30 seconds or more until a read-optimised Entity Lookup Service reduced responses to under 3 seconds, according to Commvault. The architectural shift matters because identity and access controls for modern platforms must now assume distributed services, independent scaling, and a centralized control plane.
Editorial analysis by NHI Mgmt Group, based on content published by Commvault: “Modernizing Commvault’s Architecture: From Monolith to Scalable Microservices”.
Key questions
Q: How should security teams govern a single control plane that manages many environments?
A: Treat the control plane as a privileged administration tier, not just another interface.
Q: What breaks when platform services are scaled vertically instead of horizontally?
A: Vertical scaling can postpone capacity problems, but it leaves the governance model tied to one machine and one failure domain.
Q: How do teams know whether a read-optimised lookup layer is safe for operational decisions?
A: Use it only when the team can clearly define what is authoritative and what is replicated.
Practitioner guidance
- Map privileged control surfaces Inventory which administrative consoles, service hosts, and control-plane functions can change platform-wide state, then classify them as privileged access paths.
- Separate authoritative from replicated data Document which records are system of record and which are denormalized lookup copies, especially where access or operational decisions rely on the read layer.
- Apply stronger governance to control planes Put tighter authentication, logging, and change approval around the single administrative plane than around ordinary workload nodes.
Bottom line: Vertical scaling eventually exposes a governance limit, not just a performance limit, because the platform’s operating assumptions no longer match how the services actually run.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 3:45 pm
Horizontal scale changes the identity problem from capacity to governability. Once platform services stop living on one machine, access control, administration, and audit all have to work across distributed runtime boundaries. That is not just an engineering refactor; it is a governance shift that makes single-instance assumptions unreliable. The practitioner conclusion is that identity controls must be designed for service estates, not servers.
A question worth separating out:
Q: What should IAM teams do when services can run independently across multiple machines?
A: Move from host-by-host thinking to service-by-service governance. Track each modular service’s identity, administrative scope, and lifecycle owner so scaling out does not create unmanaged access paths or inconsistent controls. Independent execution still needs central policy, but enforcement must follow the service boundary.
👉 Read our full editorial: Horizontal scale and control planes are reshaping data infrastructure