EMC’s February 2011 strategy was built around a simple idea: enterprise IT would increasingly be delivered like a service. VMware virtualization would pool computing resources, while EMC supplied storage, data protection, security, and cloud infrastructure for private, public, and hybrid environments.
That vision was directionally important, but it was not a prediction that every company would immediately move to a public cloud. It was a plan to make data-center infrastructure more flexible, automated, and service-like—and to reduce the money and effort consumed by routine maintenance.
As an Amazon Associate I earn from qualifying purchases.
What EMC announced in February 2011
The original Computerworld report was published on February 8, 2011, after EMC’s first strategic forum in two years. The audience was made up of financial analysts and investors, and CEO Joe Tucci presented cloud computing as the future platform for business IT.
Free tools Windows power users keep installed
One-click scans. No signup required.
EMC’s argument covered three deployment models:
- Private cloud: infrastructure operated for one organization, usually in its own data center or a dedicated hosted environment.
- Public cloud: computing and storage capacity supplied by an external provider.
- Hybrid cloud: an operating model that combines enterprise-owned and public resources.
The strategic objective was “IT as a service”: computing, storage, and applications would be abstracted from individual physical machines and delivered from a managed pool of resources.
#1 Best Overall
What “IT as a service” meant
EMC was not primarily describing modern software subscriptions such as email or office applications. It was talking about infrastructure and operations.
In the proposed model, resources would be pooled across servers and data centers. Applications could be provisioned according to policies rather than manually assigned to specific hardware. Standardized automation, catalogs, monitoring, and governance would make infrastructure behave more like a utility.
That could improve utilization and speed provisioning. It could also change the financial profile of IT by reducing the need to buy dedicated hardware for every application. But it did not mean that cloud automatically eliminated costs. Hardware, software licenses, employees, networking, security, data movement, and support would still have to be paid for. Cloud could shift spending, improve flexibility, or reduce idle capacity without guaranteeing a lower total bill.
Recommended Free Tools
The problem EMC wanted to solve
Traditional enterprise infrastructure was commonly organized into vertical stacks: applications depended on middleware, operating systems, servers, storage, and specialized teams. Business units often had separate capacity silos, even when their workloads had different demand patterns.
That model created several problems:
- Low utilization of dedicated hardware
- Slow provisioning and procurement
- Duplicated infrastructure across departments
- High maintenance and operations overhead
- Difficulty moving workloads between locations
- Limited ability to respond quickly to changing demand
Tucci cited an average allocation of 67% of IT budgets for maintenance and 27% for innovation or business value. Those figures should be understood as Tucci’s claim at the event, not as a universally verified benchmark for every organization.
Why VMware was central
VMware supplied the abstraction layer that made EMC’s storage and infrastructure useful in a cloud-style operating model. The 2011 article highlighted three VMware products:
- vSphere: the virtualization platform for aggregating compute resources and running workloads across a pool of servers.
- vShield: security capabilities for virtual networks.
- vCloud Director: a way to deliver virtualized infrastructure through catalogs and service-oriented management.
In architectural terms, virtualization was becoming something like a data-center operating system. It could coordinate hardware, schedule workloads, and present standardized resources to administrators and applications.
Rank #2
That did not make virtualization identical to cloud computing. A virtualized data center could remain entirely on-premises. A genuine private-cloud model also required self-service, automation, governance, standardized operations, and often metering or chargeback.
Hybrid cloud was more than “moving servers to the cloud”
EMC’s hybrid-cloud vision involved workloads and policies spanning enterprise data centers, public resources, and geographically distributed virtual data centers. The article described possible environments for areas such as marketing, sales, investment banking, retail banking, development, and production.
The goal was policy-driven placement: an application could use an appropriate resource pool based on requirements for capacity, security, availability, or business function.
That model promised flexibility, but hybrid infrastructure also introduced difficult operational issues. Organizations had to coordinate networking, identity, security, monitoring, compliance, disaster recovery, and data movement across separate environments. Large data sets could be expensive or slow to move because of data gravity and bandwidth limits.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
EMC’s storage strategy
EMC divided its storage story between established enterprise workloads and newer distributed-data requirements.
Traditional enterprise data
Symmetrix and VNX represented conventional enterprise storage for structured, mission-critical, and highly controlled workloads. These systems were associated with requirements such as availability, performance, data protection, and centralized management.
Big and distributed data
Isilon, which EMC had acquired, provided clustered network-attached storage. Atmos was positioned as a cloud-storage platform.
Rank #3
The article connected these technologies with mobile data, video, geophysical exploration, medical imaging, and gene sequencing. In 2011, “big data” was a broad term for data sets that were large, distributed, or generated by new types of applications. It did not refer only to modern machine-learning systems or today’s analytics platforms.
EMC also emphasized that data could have different values over time. Some information might be temporary, while other data would need durable, globally accessible storage with appropriate security controls.
The Data Domain qualification
EMC acknowledged a competitive gap with NetApp in block-level data deduplication. It said an upgraded version of its Data Domain deduplication product was planned for the second half of 2011.
That statement was a product-development plan, not proof that the release occurred on schedule or achieved a particular competitive result. The distinction matters when reading technology forecasts: an existing product, an announced capability, and a promised future release are different kinds of evidence.
The mission-critical test
In 2011, lower-tier applications such as email and Web applications were already being placed on virtualized or cloud infrastructure. EMC’s more ambitious goal was to move tier-one applications, including mission-critical databases, onto virtualized platforms.
That transition required more than the ability to create a virtual machine. Enterprises needed confidence in:
- Scalability and predictable performance
- High availability and resiliency
- Security and compliance
- Data mobility and disaster recovery
- Application compatibility
- Operational governance
A virtualized database could still be difficult to operate, expensive to license, or unsuitable for a particular latency and compliance requirement. EMC’s strategy was therefore a direction of travel, not evidence that every workload was already cloud-ready.
What the strategy got right
Several parts of EMC’s thesis became central to enterprise infrastructure:
- Virtualization would abstract workloads from physical servers.
- Infrastructure would increasingly be pooled rather than dedicated.
- Automation and policy would matter as much as hardware capacity.
- Enterprises would use combinations of on-premises, hosted, and public resources.
- Storage would need to accommodate rapidly growing and geographically distributed data.
- Infrastructure would increasingly be consumed through standardized services.
These ideas helped lead toward converged infrastructure, hyper-converged appliances, software-defined storage, managed hybrid cloud, and consumption-based technology services.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWhat the strategy underestimated
The 2011 vision also simplified several realities. Cloud adoption was not only an infrastructure problem. It required changes to procurement, security, application design, organizational responsibilities, chargeback, governance, and vendor management.
Virtual-machine portability did not guarantee application portability. Hybrid cloud could increase complexity rather than remove it. Consolidation could create larger failure domains. Vendor integration could simplify purchasing while increasing dependence on one ecosystem. And infrastructure savings depended heavily on workload, utilization, licensing, data-transfer requirements, and operating discipline.
The strategy also used “cloud” as a broad destination. Modern cloud-native platforms added managed databases, serverless computing, containers, observability, and developer-oriented services that were not the main focus of EMC’s 2011 infrastructure thesis.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What happened to EMC and VMware?
The corporate context has changed substantially:
- EMC held the strategic forum described in the article in February 2011.
- Dell completed its acquisition of EMC on September 7, 2016, creating Dell Technologies and the Dell EMC enterprise business.
- Dell Technologies later spun off VMware as a standalone company in 2021.
VMware therefore should not be described today as an EMC or Dell Technologies subsidiary. The 2011 product names—vSphere, vShield, vCloud Director, Atmos, Symmetrix, and VNX—should likewise be treated as historical portfolio references, not automatically as current product recommendations.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →How the product thesis evolved
Later Dell EMC announcements showed the same broad direction continuing through integrated and software-defined infrastructure.
Best Value
VxRail combined EMC data services with VMware virtualization and software-defined storage in a hyper-converged appliance. A 2016 announcement listed a starting price of $60,000, but that was a historical list-price signal—not a current price.
Other later examples included ECS object storage, software-defined Data Domain data protection, Unity storage, cloud tiering, and service dashboards. These products illustrate the movement toward integrated infrastructure and hybrid operations, but they do not prove that one architecture is cheapest or best for every workload.
What this means for technology budgets
For CIOs and infrastructure planners, EMC’s most useful lesson is not “buy cloud.” It is to evaluate how infrastructure is consumed.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Predictable, heavily utilized workloads may justify owned infrastructure.
- Variable workloads may benefit from public-cloud elasticity.
- Regulated or latency-sensitive systems may favor private or hosted infrastructure.
- Large data sets may make locality and egress costs more important than headline compute prices.
- Organizations with mature VMware estates may value operational continuity, while new deployments may prefer managed cloud-native services.
Public-cloud services from Amazon Web Services, Microsoft Azure, and Google Cloud represent a different way to pursue the same broad outcome: consume infrastructure without owning every layer. Private-cloud infrastructure and current virtualization platforms pursue more control, but require more operational responsibility.
Bottom line
EMC’s 2011 strategy was not simply a storage-company pitch for moving servers online. It was a plan to combine VMware’s abstraction and management layer with EMC’s storage and data services, creating a flexible infrastructure pool that could span private, public, and hybrid environments.
The forecast was broadly right about virtualization, pooled infrastructure, automation, hybrid deployment, and service-oriented consumption. It was less complete about the organizational cost, application complexity, data-movement constraints, and cloud-native services that would shape the next phase. EMC’s products and corporate structure changed, but the underlying question remains relevant: which parts of IT should an organization own, automate, outsource, or consume as a service?
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
