Skip to content

Comment on Why we shift testing left: A software dev cycle that doesn’t scaleparent

Comments

ROAC is a pipe dream (I used to believe in it also)

most large cloud/distributed systems cannot be realistically reproduced in your compose/k3s/whatever environment

a large cloud/distributed system must be tested on something similar in scale

at best, ROAC lets you do some development remotely/offline, but is not a reliable model of reality

We have decided not to use anything that can't run any any computer. It's really possible to have large scale systems ROAC, if you pay attention to avoid proprietary cloud tech lock-in.

(ROAC in our case means Runs on any Kubernetes)

Anything interesting and server-based usually depends on an entire complex data pipeline (one system for this if you’re lucky) and a dozen or more external systems with no great way to mock them that won’t itself be out-of-sync with reality often, anyway.

I once heard Facebook uses production database to develop and test new feature because anything else was unfeasable. Even a smaller copy of it.

I'd love to have a confirmation from someone at Meta.

edit: found an amazing discussion about their release process here: https://news.ycombinator.com/item?id=30899362

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.