But the server already exists. You are already paying for it's existence as it handles other things. This is common if you worked for an IT company. In short:

But the server already exists. You are already paying for it's existence as it handles other things. This is common if you worked for an IT company. In short: The server is the origin of the task. By definition the task doesn't exist without the origin/trigger. Why spend extra on a lambda? I think you're lost. Especially if you built architecture like this where servers wait for lambdas that just wait for database calls. (FYI waiting time is slightly longer this way, cost is slightly more expensive, and architecture becomes unnecessarily complex) Literally first reply is someone who thinks a lambda is the right tool. I wasn't sure how bad it was until this young man replied.