3 ms·
> You deploy, get an error message, and login to CloudWatch to see what actually happened - it’s all batch-driven, just like the bad old days, so progress is sl
by pensatoio 6y ago
> You deploy, get an error message, and login to CloudWatch to see what actually happened - it’s all batch-driven, just like the bad old days, so progress is slow.
You can run and test FAAS, even the proprietary Lambda, locally. In fact, if you aren’t doing so, I dare say you’re “doing it wrong.”
Lambda is just one more tool in the tool chest of pluggable components that scale infinitely. “Given input X, do Y,” is boiled down to a predictable, repeatable service that requires almost zero infrastructure knowledge.
- greenie_beans 6y agoWe were definitely doing it wrong at my last job. We had 200+ lambda functions (a lot of redundant lambdas that were breaking DRY rules). Each function was terraformed and there was no way to provision the AWS resources to run the lambdas locally. So whenever I made a lambda, I wrote all of my code locally without testing and then had to push it up to delpoy. Then I could run it and debug in the console. Nightmare. It was even worse with batch.