This article is based on analysis originally published by Gigabit Magazine (gigabitmagazine.com).
It is no longer a surprise that the volume of enterprise data is growing rapidly. What is less widely discussed is that the origin of that data is shifting just as fast. An increasing share of data is now being generated in the cloud and at the network edge, not in traditional data centres. This shift forces engineering and operations teams to rethink where and how they analyse, understand, and manage data — ideally without routing everything through a centralised data centre as an intermediary.
Three areas are experiencing the most significant change when it comes to enterprise data strategy:
1. Edge Data Requires Edge Data Management
Edge computing buildout is already well underway, and its pace is accelerating. Key drivers include the Internet of Things (IoT), autonomous vehicles, and biometric systems — all of which generate large volumes of data far from centralised infrastructure. According to IDC forecasts cited in the original source, 50% of all enterprise IT infrastructure could be deployed at the edge by 2023, compared to roughly 10% at the time of writing.
This creates a straightforward operational challenge: if data is being generated at the edge, why move all of it to a data centre before you can do anything useful with it? The answer increasingly is that you should not. Edge data management addresses this by allowing teams to:
- Analyse data locally at the point of generation.
- Classify which data is high-value and needs to be sent back to the data centre or cloud for deeper processing.
- Process or discard lower-value data directly at the edge, reducing bandwidth costs and latency.
As more applications are purpose-built for edge deployment, the tooling around edge data management — including lightweight databases, stream processing, and local orchestration — will grow in maturity and adoption.
2. Multi-Cloud Adoption Makes Cross-Cloud Data Management a Requirement
Most large enterprises using public cloud services have already adopted some form of hybrid or multi-cloud strategy. Rather than committing to a single cloud provider, organisations are increasingly distributing workloads across two or more clouds — whether for cost optimisation, resilience, regulatory compliance, or to avoid vendor lock-in.
The operational consequence is data sprawl: copies of data, pipelines, and storage systems spread across AWS, Azure, Google Cloud, on-premises infrastructure, and potentially the edge. Managing this sprawl is genuinely difficult when each cloud provider offers its own native data tools with proprietary interfaces.
Cross-cloud data management platforms aim to solve this by providing a unified layer to discover, catalogue, govern, and move data regardless of where it physically resides. Key capabilities engineering teams should evaluate in such platforms include:
- Vendor-neutral connectivity: Integration with multiple storage and compute providers without requiring data to be normalised into a proprietary format.
- Unified metadata and cataloguing: A single view of what data exists, where it lives, and who owns it.
- Policy-based governance: Consistent access controls, retention policies, and compliance rules applied across all environments.
- Data portability: The ability to move or replicate data across clouds without manual re-engineering.
As multi-cloud becomes the default rather than the exception, solutions that are tightly coupled to a single cloud vendor’s ecosystem become a liability rather than an asset.
3. Analytics-Driven AI Moves from Buzzword to Operational Tool
Artificial Intelligence (AI) and Machine Learning (ML) have been prominent themes in enterprise technology conversations for several years. For much of that time, they occupied a space somewhere between genuine potential and marketing overstatement. That balance is shifting.
The application of AI to data management itself — rather than just to business analytics — is where some of the most practical near-term value lies. The core idea is straightforward: you cannot manage data you do not understand. By applying ML models to analyse data characteristics, usage patterns, access frequency, and content, data management platforms can make better automated decisions about storage tiering, archival, deletion, access control, and anomaly detection.
Concretely, analytics-driven AI in data management can enable:
- Intelligent data tiering: Automatically moving cold data to cheaper storage without manual intervention.
- Anomaly and threat detection: Identifying unusual data access patterns that may indicate a security incident.
- Data quality improvement: Flagging duplicate, incomplete, or inconsistent records across distributed repositories.
- Capacity forecasting: Predicting storage growth trends to inform infrastructure planning.
Data lakes spanning multiple storage repositories provide the breadth of signal needed to train and refine these models effectively. The practical output is a management layer that becomes smarter over time — reducing toil for operations teams while improving data hygiene across the organisation.
Bringing It Together: Manage Data Where It Lives
The common thread across all three of these trends is a shift away from the assumption that all data must eventually pass through a central data centre before it can be properly managed. That assumption made sense when almost all enterprise data was generated on-premises. It is increasingly untenable when data is being produced continuously at the edge, in multiple clouds, and across distributed application stacks.
Engineering and operations teams that get ahead of this shift will invest in:
- Edge-native data management tooling that reduces unnecessary data movement.
- Cloud-agnostic governance platforms that work across all environments without vendor lock-in.
- AI-assisted analytics that help teams understand and act on data at scale without proportionally growing headcount.
The organisations that treat data management as a first-class engineering concern — rather than an afterthought bolted on after architecture decisions are made — will be best positioned to derive real value from their data wherever it happens to live.