4 ms·
I'm currently migrating to Kubernetes. Hard to tell where things go in 3yrs (the pace of change is so high, a year seems like forever)...BUT...a couple of thing
by TuringNYC 9y ago
I'm currently migrating to Kubernetes. Hard to tell where things go in 3yrs (the pace of change is so high, a year seems like forever)...BUT...a couple of things that drove me to the migration:
1 - Less stickiness to AWS since the serverless architecture would abstract away the provider and i could theoretically even grab the cheapest spot instances across providers (AWS, Google Cloud, SoftLayer, Azure)
2 - Lower compute bills (due to better usage and being able to more tightly pack stuff into nodes)
3 - Lower HR bills due to a lot of stuff just scaling up without effort rather than dozens of deployment/babysitting staff
Hard to know for sure, but these are the three things that drove me to Kubernetes.
- BatFastard 9y agoBut I find some type of persistence of data usually figures into my serverless calls. And those tend to lock you into a vendor. Especially when you want to start analysing the data you have. Even if you could separate them it would add latency. Now if it JUST compute... and I can see that as a possibility for some CV applications.