I don't, I guess ;) We used lambda since quite early days but in almost every case we regretted it in the end. It always turned out that Kubernetes with some application processing (eg. Sidekiq) scales better, performs better and we have better insight into what's going on if something goes wrong.
I don't, I guess ;) We used lambda since quite early days but in almost every case we regretted it in the end. It always turned out that Kubernetes with some application processing (eg. Sidekiq) scales better, performs better and we have better insight into what's going on if something goes wrong.
Hahah yes, definitely there are draw backs when it comes to serverless, I think it's all about the project at the end of the day.
Your final point is the most important to me, transparency is actually key for when (not if) something goes wrong :)