2 ms·
Simple but inconvenient. And it doesn't take much to get sucked into cloud lock-in. As soon as you need to work on permissioning that is slightly less trivial y
by gchamonlive 2y ago
Simple but inconvenient. And it doesn't take much to get sucked into cloud lock-in. As soon as you need to work on permissioning that is slightly less trivial you start to sink.
- j45 2y agoCould permissioning not be run along the packaging to keep things cloud agnostic? Some days I wish there was an entire HN devoted to self-hosting and cloud-agnosticity lol.
- fragmede 2y agothe problem is there's not an exact 1:1 mapping between clouds, so there's complexity to hold in your head. gcp project, aws account, and azure subscription don't represent exactly the same thing, so at some level you can paper over the differences but you really can't, once you get into the nitty gritty of it, so then you're left building up expertise as a multi-cloud software engineer that knows those subtle differences.