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.
HN community, we've gone serverless at my startup for the last 2.5 years, and I've seen its advantages on scalability, dev velocity, and cost efficiency. Like any other new technology, it's not a cure-all solution and may not be the right fit for some applications. But I'd argue that in the long-term it will be the de-facto solution for a vast majority of cases.I've published a write-up on...