5 ms·
"Let that be a lesson to not rely on cloud infrastructure too much without designing your architecture to be somewhat cloud agnostic." Not disagreeing per se,
by CrLf 8y ago
"Let that be a lesson to not rely on cloud infrastructure too much without designing your architecture to be somewhat cloud agnostic."
Not disagreeing per se, but I believe it's much more important to design for migration between providers instead of designing for abstraction over providers. The difference is subtle, but trying to make predictions about what needs abstraction will most likely lead to the same (or bigger) costs when a migration actually happens.
It's a bit like the general advice to design to avoid getting stuck in a hole as opposed to designing to getting out of future holes.
- gaius 8y agoI believe it's much more important to design for migration between providers instead of designing for abstraction over providers Right. If you design to be cloud agnostic that means only using the lowest common denominator of features, and while it’s doable it’s not cost effective. The price structure is designed to shepherd you into the managed services.
- bfirsh 8y agoThe thing that drew me to Hyper.sh in the first place was the fact that it used the Docker Remote API. That gave me some confidence it would be provider agnostic. Unfortunately no other providers have done this, so that idea didn't pan out.
- slackpad 8y agoI thought Joyent had a container service that used the Docker Remote API?
- philipswood 8y agoJoyent Triton https://www.joyent.com/triton/compute https://www.joyent.com/triton/compute A few years ago (when I last checked} their container startup times were a lot slower than hyper.sh's