I'd argue the most important value prop that serverless has had for us was to force us think of everything in terms of an event-driven process, with small batches of job being done at every invocation. This is such an underrated benefit of going serverless/event-driven: together with job queues, this has enabled us to maintain control of our jobs from outside the code, without a need for re-deployment. We can fast-forward, pause, stop, rewind our long-running jobs simply by changing the event triggers or sending a new message to the queue.