Section IV · The Digital Revolution & Its Critics
Larry Ellison
Data, Databases, and the Control of Information Systems
To understand Larry Ellison, you have to begin with a systems question: what happens when data becomes the core asset of organizations?
As businesses, governments, and institutions digitized their operations, information moved from paper to structured databases. The challenge was no longer just storing data — it was organizing, securing, and retrieving it efficiently at scale.
Ellison built for that layer.
At the center of his worldview is a defining claim:
Control over data systems creates durable enterprise power.
As the co-founder of Oracle, Ellison focused on relational database software — systems that allow organizations to structure, query, and manage large volumes of information. These databases became foundational infrastructure for finance, logistics, healthcare, and government operations.
From this perspective, data is not passive. It is an operational asset. Organizations depend on accurate, accessible data to make decisions, coordinate activity, and execute strategy. The systems that manage this data become deeply embedded and difficult to replace.
This creates a specific form of power:
High switching costs and long-term dependency.
Once an organization builds its operations around a database system, migrating away becomes complex and expensive. This gives providers like Oracle a stable and enduring position within enterprise ecosystems.
Ellison extended this model. Oracle expanded from databases into enterprise software, cloud infrastructure, and integrated systems, aiming to control multiple layers of the data stack. The goal was not just to store data, but to manage the full lifecycle of information.
This reflects a broader framework: Economic power increasingly resides in enterprise infrastructure that is invisible to end users.
Supporters see Ellison as a builder of mission-critical systems.
They argue that Oracle enabled organizations to manage complexity, improve efficiency, and scale operations globally. Reliable data systems are essential for modern economies, and Oracle helped standardize how they function.
From this perspective, Ellison expands the analysis of economic systems to include enterprise data infrastructure as a central pillar.
Critics, however, raise important concerns.
They argue that proprietary systems can lock organizations into costly, inflexible arrangements. Licensing models, pricing strategies, and vendor control have been frequent points of contention.
Critics also point to a broader issue: when data infrastructure is concentrated, organizational autonomy can be constrained.
A deeper tension lies in the relationship between reliability and dependency. Systems that provide stability and performance can also limit flexibility and bargaining power. Who controls the data, and who controls the systems that manage it?
Ellison’s continued expansion into cloud computing reflects an effort to maintain this position — shifting from on-premise systems to remote infrastructure while preserving control over enterprise data environments.
Larry Ellison did not invent databases. But he helped make them the backbone of modern organizations — demonstrating how control over data systems can translate into long-term economic power.
His legacy raises enduring questions: Who controls the infrastructure that stores and manages critical data? How should dependency on enterprise systems be governed? And what is the balance between performance, security, and autonomy in the data-driven economy?