11–17 of 17 posts
This way, the deployment issue of an application and its maintenance kind of goes away. It's also free, meaning I don't have to spend any more money or pack the code in another server.
As I like to joke, I am a simple liberal arts major...with about 24 years on/off Wall Street. Have been an intermediate user of R seemingly forever. While I find node.js painful, early days still, the capabilities that I have and will have in the near future to improve my Shanghai based professional services business speaks to the power of the technology/framework, whatever you want to call it. Working on a Hugo webs…
The million at once thing happens more often then you think, take the case where a website gets a new logo. Now you have to redo the watermark on all the images. Or maybe you want to convert your jpg to webp.
You can also use lambdas to process your images on-the-fly as clients request them. We use both pre-process and on-the-fly depending on if we need hashes ahead of time.
That means you won’t have to preallocate (and pay for) resources that will go unused during non-peak load. It enables automatic scaling.
There are plenty of “serverless” offerings for computation, but very few for databases. Without the later, I don’t think it has much value.