'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/

16•genericlemon24•9h ago

Comments

jasode•7h 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•7h 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•6h 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•6h 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.

Show HN: ClipBin – The Simplest and Secure Way of Sharing Text/Code

Gumroad CEO's playbook to 40x his team's productivity with v0, Cursor, and Devin [video]

Consumers make their voices heard as Microsoft's venture flatlines in popularity

Why more people than ever before are running marathons

Show NW: Announcing Nest2D.dev: Open-Source Server-Side Nesting for DXF

Apple Conformer-Based Speech Recognition on Extreme Edge-Computing Devices

Designing A New Postgres Storage Layout for Search

Gemini Flash Pretraining

Wanix: The Spirit of Plan 9 in WASM

Vim in Robotics

Do Large Language Models know who did what to whom?

Marknotes: Simple Blog Built Using Go and HTMX

India to begin construction of gravitational wave project

AI can handle tasks twice as complex every few months

Robin Hanson on the Age of AI and Large Language Models

Lenovo May Be Avoiding 'Windows Tax' via Cheaper Laptops with Preinstalled Linux

Show HN: Collection of free AI tools to get your job done faster

Purchasing a Domain in 2025 – Enshitiffication

Gravity: The Universe Keeping it (computationally) Tidy?

Macros in the Dart Programming Language

Trump admin says it wants a nuclear Renaissance. These actions suggest otherwise

LiDPM: Rethinking Point Diffusion for Lidar Scene Completion

The cryptoint library (DJB) [pdf]

MCP Is Unnecessary

LLVM adds processor definition for XiangShan-KunMingHu-V2R2

A new map of arthropod evolution, from fossils to embryos

Developing this blog in Go and HTMX

WebGL Black Hole

Apple's SillyBalls

The BeOS file system, an OS geek retrospective