Choosing between a cloud-hosted and a locally hosted database is rarely just a technical decision — it is a financial one. A local deployment usually means buying servers, storage, and networking gear up front, paying for perpetual or per-core database licenses, and staffing people to patch, back up, and monitor the system. A cloud deployment shifts most of that into a recurring bill that scales with what you consume, but that bill never ends and can grow quickly if workloads are not sized and managed carefully.
This topic gives you the vocabulary and the analytical frame for that comparison: capital expenditure (CapEx) versus operational expenditure (OpEx), hardware and refresh cycles, licensing differences between on-premises and cloud editions, ongoing operational and maintenance labor, and how elasticity changes the cost-efficiency equation. The goal is Total Cost of Ownership (TCO) thinking — accounting for every cost over a multi-year horizon rather than comparing a server price tag to a monthly subscription.
As you watch the videos below, listen for three things: how each cost is classified (one-time versus recurring), who absorbs the cost under each model, and what assumptions drive the answer — workload steadiness, utilization rates, growth rate, and staffing. Those assumptions are usually what decide whether cloud or local comes out cheaper for a given organization, and you will be expected to state them when you make a recommendation.
A short lecture on cloud cost models that defines capital expenditure and operational expenditure and explains consumption-based (pay-as-you-go) pricing. Based on its title and description, it should walk through how each model affects budgeting and when an organization would prefer one over the other.
It directly addresses the central CapEx versus OpEx distinction of this topic in a compact, lecture-style format, and Gate Smashers presents computing concepts in exam-ready, clearly structured terms.
An IBM lightboard explainer on serverless computing, covering what serverless means, how resources are provisioned on demand, and how billing is tied to actual execution rather than reserved capacity. It is likely to contrast this with traditional always-on server provisioning and to touch on the operational work the provider absorbs.
Serverless is the clearest illustration of consumption-based pricing and elastic scaling, which makes it a useful lens on the scalability-and-cost-efficiency subtopic and on which operational duties shift to the provider.
An Oracle technical deep dive on consolidating multiple databases onto shared infrastructure, both on Exadata on-premises and in the cloud, as a strategy for lowering cost. Expect discussion of utilization, resource sharing, and features that let many database instances coexist on the same hardware or service.
It brings in the vendor-side realities of hardware and licensing economics and shows that cost reduction is not only a cloud-versus-local choice but also a matter of how efficiently capacity is used in either model.
Together these videos build the financial half of the module. The CapEx/OpEx lecture supplies the core cost-structure vocabulary needed for MO2 and feeds directly into TCO reasoning. The serverless explainer makes the consumption-based, elastically scaled cloud model concrete, supporting MO1 and MO3 and hinting at the division of duties you will formalize under the shared responsibility model in MO5. The Oracle consolidation deep dive grounds the discussion in real hardware, licensing, and utilization decisions across both on-premises and cloud environments, giving you the kind of evidence needed to weigh maintenance and efficiency trade-offs and recommend a hosting strategy for a specific organization as required by MO4.
These videos were chosen from YouTube on October 2, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.