The Cloud Tipping Point [YouTube Release]

Youtube Releases
1

Additional Resources:

“Just put it in the cloud.”

It sounds simple, but is it always the right answer? In this presentation from the 45Drives Creators’ Summit 2025, I explore the tipping point between cloud services and self-hosted infrastructure - when moving to the cloud makes sense, and when you’re better off running on-premise or in a colocation data center.

This is a business-oriented discussion covering the real costs, benefits, and trade-offs of cloud vs. on-prem, including security, scalability, and long-term sustainability. While it’s aimed at IT professionals and decision-makers, homelab enthusiasts, and anyone maintaining networks will also find valuable insights.

Thanks to Meter for sponsoring this video!
Go to Meter – Network infrastructure for the enterprise to book a demo now!

Connect With Us

Lawrence Systems Shirts and Swag

►👕 Lawrence Systems

AFFILIATES & REFERRAL LINKS

Amazon Affiliate Store
:shopping_cart: Lawrence Systems's Amazon Page

UniFi Affiliate Link
:shopping_cart: Ubiquiti Store

All Of Our Affiliates help us out and can get you discounts!
:shopping_cart: Partners We Love – Lawrence Systems

Gear we use on Kit
:shopping_cart: Kit

Use OfferCode LTSERVICES to get 10% off your order at
:shopping_cart: Tech Supply Direct - Premium Refurbished Servers & Workstations at Unbeatable Prices

Digital Ocean Offer Code
:shopping_cart: DigitalOcean: AI-Powered Unified Inference Cloud Infrastructure

HostiFi UniFi Cloud Hosting Service
:shopping_cart: HostiFi - Fast and Reliable UniFi in the Cloud

Protect your privacy with a VPN from Private Internet Access
:shopping_cart: https://www.privateinternetaccess.com/pages/buy-vpn/LRNSYS

Patreon
:money_bag: https://www.patreon.com/lawrencesystems

Chapters
00:00 The Cloud Tipping Point
01:08 The Cloud is not bad
02:48 Startup Businesses
04:03 The Commission Problem
05:39 Cloud Cost History
06:49 Then Came the Fees
07:50 Defining the Tipping Point
08:05 Cloud Security and Shared Responsibility Matrix
10:07 Cloud Management
10:45 Cloud Bench marking
12:16 Cost Comparison of Cloud and on Prem Performance
14:35 ZFS and CEPH
16:14 Open Source Storage Management
17:49 Open Source Virtualization
19:08 Refurbished Hardware
21:09 Real Word Analysis by 37 Signals

2

Just watched this and wish I could get another department at work to watch this… I think we spend a huge amount per month on either AWS or Microsoft, money that could be brought back in house. We also have multiple buildings all connected by 25gbps which would make a nice backbone for nightly transfers. The probability of an event destroying 2 buildings down to the basement over the area we cover is significantly low, and we could certainly add more buildings to reduce the risk.

Your CAPX vs OPX slide points this out really nicely, and if you lower the speed of the storage to spinning drives, you can lower that buy in significantly (per terabyte).

4

I haven’t watched the video so maybe it was touched on.

I recall the times prior to moving applications / systems / data offsite, there were huge departments involved in keeping this all going, none of it was core to the banking business. Reduce headcount, reduce costs, move non-core operations to a 3rd party, increase profitability.

A lot of know-how have left organisations and bringing back these functions would be quite painful for sure. However, organisations love change and if it saves a penny then they are prone to act if the Execs can look good.

5

I think the video did a good job highlighting cost and performance as key reasons for choosing one option over another. However, it’s also important to consider factors like security and resiliency (RTO/RPO).

For instance, if you need to protect against potential DDoS attacks or ensure aggressive application uptime targets, cloud solutions may be the better fit. Cloud can also simplify the deployment of new applications, especially those built around microservices.

Among the four main factors of cost, performance, security, and resiliency I’d suggest that cost is often the least critical. In practice, security, resiliency, and performance typically carry more weight. I say this from experience, even after being responsible for managing budgets in this area.

The key question to ask is: what’s at stake if the application goes down? Let the business requirements and risk tolerance drive the architecture. Cost will always matter, but it should be one consideration among many and not the primary one.