Two options we use, database used as a queue for granular out of process work. If something errors, we'll get a notification for that one record, but the rest w

Two options we use, database used as a queue for granular out of process work. If something errors, we'll get a notification for that one record, but the rest will keep processing. For stuff that we don't need such granularity/replay, we use Amazon's SNS event framework to trigger different APIs. Sometimes we do a combination of those, an SNS event triggers a lambda that puts a record in the database queue, which gets picked up by a job engine and raises an SNS event that hits an API that sets a record to available.