> If you are already paying for EC2, running those short-lived cron jobs in any one of those instances already adds zero cost. Now you have a scheduling/orches

> If you are already paying for EC2, running those short-lived cron jobs in any one of those instances already adds zero cost. Now you have a scheduling/orchestration concern. Kubernetes was built to address that kind of concern. The thread is filled with people bemoaning the cost of running Kubernetes. > The main beneficiary of AWS Lambdas is AWS itself. It charges a huge premium for what essentially amounts to spare cycles in its infrastructure, and in the process ties up clients to a proprietary solution. And as a result, we (the customers) don't have to pay for infrastructure that would otherwise be idle. Why can't it be a win-win?