2,885 karma · joined March 14, 2012
Co-founder, Kami - kamiapp.com
IMO it's not really about having the resources to scale, but the unpredictable emergent behaviours which can happen when the load profile suddenly changes
My pet theory wasn't too popular but I'm going to stick with it :)
The compass is still terrible though!
https://www.nasa.gov/leo-economy/commercial-use/pricing-poli...
It's pretty noticeable here in New Zealand where most people are now on fiber connections with easily enough bandwidth and low latency - but video calling is still way harder than it should be.
If you've read anything about what they were like as a band that's quite a career path!
It's not aimed at the kind of person who prefers a flashy presentation over substance, which in this case is extremely rapid progress towards the most capable rocket humanity has ever built.
- Rollbacks
- Automatic deployment of new releases from CI, rolling releases
- Healthchecks, detecting if/when the server exits and making sure that VM gets killed
- Canary deployments
- Autoscaling (could use an autoscaling instance group for it, but what if you need to scale based on other metrics)
- Log aggregation
- Monitoring
- Service discovery, load balancing between services
- Service mesh
- Fast startup of instances (starting a fresh VM and waiting for it to setup everything from scratch could take ~3-4 minutes, docker is in the ~30s or less range).
- Bin-packing (run a high-cpu low-memory workload colocated with a low-cpu high-memory workload for maximum efficiency)
etc, etc, all of which you get either out of the box or without a huge amount of work if you adopt something like Google Kubernetes Engine (which takes a few clicks to spin up a cluster).
If you don't need any of that stuff and don't want to learn Kubernetes, it's totally justifiable to go that way, but personally I would take Google Kubernetes Engine over something like that any time. There's some up-front cost learning how it works which then pays off very quickly.