From the course: AWS Essential Training for Developers

Unlock the full course today

Join today to access over 23,100 courses taught by industry experts.

Managing long-running jobs

Managing long-running jobs

- Remember our lambda functions? These are great for code that runs quickly, but a single execution can't run any longer than 15 minutes. If you have a job that needs to crunch a bunch of data or wait on something to come back from a service or database, you'll need to look at the services that AWS has for batch processing and workflows. You can use the messaging services that we talked about earlier, like SQS, within your lambda function, and that could be the trigger to kick off a batch processing job to say, resize a bunch of images. Or it could be the start of a more complicated workflow where say an image is processed, someone manually reviews it sometime in the future, and it goes through another layer of processing and is reviewed again. In other applications, I've seen these jobs handled by either having a long running process within the app somewhere, and that's not good for the server, or there's a cron job…

Contents