4 ms·
Ugh, I rewrote my serverless service for exactly these reasons. It felt magical the first time where you can deploy a service without spinning up a server so I
by neurostimulant 6y ago
Ugh, I rewrote my serverless service for exactly these reasons. It felt magical the first time where you can deploy a service without spinning up a server so I put up with all these annoyances. But then docker gains popularity and suddenly there is no practical advantage in using serverless anymore, at least for me. I rewrote the service in django, packaged it as a docker image, then run it on any platform that can run docker.
On the other hand, I use cloudflare worker on a bunch of my projects. Unlike aws serverless, cloudflare worker is actually useful because it can do many things that can't be done by traditional backend, such as running and intercepting requests on the edge servers that sit between your server and your visitors.
- Dunedan 6y agoWhat you do with CloudFlare Workers can be done on AWS with Lambda@Edge [1]. [1]: https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.htm...
- neurostimulant 6y agoI can't comment on lambda@edge as it wasn't available when I was still using aws lambda a few years ago. My current use case is probably supported on lambda@edge if I were still on aws as I'm mostly only use them to implement smart caching and routing.