'Going to the cloud' could also mean locking into a forever sub-contractor

https://berthub.eu/articles/posts/beware-cloud-is-part-of-the-software/

20•genericlemon24•9mo ago

Comments

jasode•9mo ago

>This means we have enormous control over what is going on. The combined software meanwhile runs on databases and services which we also run ourselves. [...] A well known example is the Netflix streaming service, which consists of Netflix-owned hardware that streams stupendous amounts of video using very limited space in a data center. Netflix would simply not be economical if they did not have full control over the stack.

That blog paragraph presents an incomplete and inadvertently misleading architecture of Netflix.

Netflix actually uses AWS and is very much "locked in" to Amazon's cloud ecosystem. The specific item the author is talking about is the Netflix CDN "appliance" that is installed at edge datacenters. However, those appliances can be seen as a "dumb box". The "smart management" of the CDN is controlled by Netflix code deployed on databases and servers at AWS. Also, the Netflix customer accounts, billing, recommendation systems runs on AWS.

https://www.google.com/search?q=netflix+AWS+manage+CDN

bob1029•9mo ago

I would summarize my experience of different cloud technologies as follows:

Good: EC2, Route53, S3, identity provider (IdP)

Bad: Functions as a service, hosted SQL, weird SQL, elastic anything, containers, logging, reporting, billing, IoT, CI/CD, business apps, event-based services.

I used to consider IdP to be a "bad" cloud technology until I realized it's a trust problem and not a technology problem. I don't want to be responsible for a trust problem. The other parties involved in my contraptions seem to appreciate this perspective.

junto•9mo ago

I’d probably tend to be ok with the standard hosted SQL, since replication is kind of built in to most databases so getting out isn’t much of an issue. However migrating away from a cloud specific IdP is much harder and has some serious lock in.

spilldahill•9mo ago

You can really feel the tension between short-term shipping and long-term survivability here. The incentives almost always push toward deeper integration today, and someone else deals with the migration crisis five years later. ...honestly, just having basic rules like "only use cloud services that have open equivalents" would save a lot of pain later, but it feels rare to see that kind of governance actually enforced.

OpenBSD Copyright Policy

OpenClaw Creator: Why 80% of Apps Will Disappear

What Happens When Technical Debt Vanishes?

AI Is Finally Eating Software's Total Market: Here's What's Next

Computer Science from the Bottom Up

Show HN: I built a toy compiler as a young dev

You don't need Mac mini to run OpenClaw

Learning to Reason in 13 Parameters

Convergent Discovery of Critical Phenomena Mathematics Across Disciplines

Ask HN: Will GPU and RAM prices ever go down?

From hunger to luxury: The story behind the most expensive rice (2025)

Substack makes money from hosting Nazi newsletters

A New Crypto Winter Is Here and Even the Biggest Bulls Aren't Certain Why

Moltbook was peak AI theater

Why Claude Cowork is a math problem Indian IT can't solve

Show HN: Built an space travel calculator with vanilla JavaScript v2

Why a 175-Year-Old Glassmaker Is Suddenly an AI Superstar

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

These White-Collar Workers Actually Made the Switch to a Trade

The Wonder Drug That's Plaguing Sports

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

Federated Credential Management (FedCM)

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

The Story of Heroku (2022)

Obey the Testing Goat

Claude Opus 4.6 extends LLM pareto frontier

Brute Force Colors (2022)

Google Translate apparently vulnerable to prompt injection

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

Software development is undergoing a Renaissance in front of our eyes