3 ms·
I can see how someone would misunderstand that claim though: the idea of getting up and running on a new hosting provider that quickly seems so unlikely that th
by simonw 6y ago
I can see how someone would misunderstand that claim though: the idea of getting up and running on a new hosting provider that quickly seems so unlikely that thinking "well they must be talking about container launch times here instead" is an understandable mistake.
- throwaway894345 6y agoContainer launch times are frequently in minutes if we include pulling the images from a repo, which we reasonably should. In whichever case, that doesn't mean we can't compose them into a performant product as the OP suggests, it just means you run them as daemons so you can amortize the startup cost across many invocations. This isn't specific to containers--we do the same thing for web servers, databases, virtual machines, physical machines etc. Anything with a startup cost that you don't want to pay each time.
- pm90 6y agoWhy would you include pulling the container image as something that should be a part of the container launch time? It’s a one time event after a code push.
- mrkurt 6y agoIt's not a one time event, each host that runs a container image needs to pull it at least once. Minimizing pulls is a good optimization but you have to work pretty hard to really cut them down.
- tptacek 6y agoOh, you’re right; I’m just clarifying. The perils of trying to fit your whole project into a tiny lead paragraph. :)
- lsb 6y ago"Create your first project in minutes. Create your next project in under 25 seconds."
- vhodges 6y agofwiw, I moved my prod env from a VPS (at linode) to fly.io twice in one week. Once to try it out and get a feel for what I was getting into and the second time for real. Took about 90 minutes each (plus some thinking time and doc reading). It's a small app without a ton of data to move nor a lot of traffic at this point, so take my experience with a grain of salt.