4 ms·
There will likely be very few cold starts when the whole monolith is running in it
by JanSt 3y ago
There will likely be very few cold starts when the whole monolith is running in it
- SOLAR_FIELDS 3y agoAt that point you’re just paying an exorbitant rate for… the same thing you would get from hosting it on EC2
- danpalmer 3y agoOr if you can take a bit of up-front setup cost, running it on GKE with Autopilot means you've got many of the benefits of lambda on a K8s cluster (e.g. immutable container-driven development, no need to manage long-running VMs) and only pay for used resources (not idle machines). The main caveat is no scale-to-zero, but as mentioned previously, that's unlikely to happen.
- mplewis 3y agoIMXP, autopilot is multiple times the price of a VM on a non-GCP platform.
- danpalmer 3y agoHow come? I see Autopilot is $0.10 per cluster hour, or ~$75 a month, add the standard GKE cluster management overhead of $150, that's $225 a month for a cluster which rounds to zero given any reasonable load. Then in my experience GCP VMs have always been price competitive with basically any other cloud provider. The issue we had was getting the bin-packing right on our cluster, and we often ended up with 20% unallocated capacity per VM. Autopilot basically solves that (and probably pays for itself with only a few VMs) as you only pay for the K8s defined resources, and therefore only have 1 level of cost optimisation at the pod level, rather than 2 at the pod and VM level.
- JanSt 3y agoYeah, I wouldn‘t do it