3 ms·
> No persistent connections As far as I know, at least AWS has two WebSockets based services. > Expensive I think there are use-cases that are rather expensi
by k__ 7y ago
> No persistent connections
As far as I know, at least AWS has two WebSockets based services.
> Expensive
I think there are use-cases that are rather expensive to solve with serverless technology, like realtime games and such, but overall? I don't know... many companies I've seen using serverless aren't even getting out of free-tier.
> Limited programming language availability
At least AWS has allows to bring your own runtime, it just has to be compiled for Amazon Linux 2.
> No local state
I don't think this is a good thing, but I think Azure does something like that with Durable Functions.
> Cold starts.
Only a problem if you use FaaS and that isn't a requirement for serverless. At least AWS allows to build some types of serverless applications without Lambda. For example APIs can be build with API-Gateway alone or AppSync.
- soygul 7y ago> As far as I know, at least AWS has two WebSockets based services. True. WebSocket APIs in Amazon API Gateway looks good and is accessible from Lambda functions. Didn't try myself though: https://aws.amazon.com/blogs/compute/announcing-websocket-apis-in-amazon-api-gateway https://aws.amazon.com/blogs/compute/announcing-websocket-ap... > At least AWS has allows to bring your own runtime, it just has to be compiled for Amazon Linux 2. I did not know this. I will check it out. > Azure does something like that with Durable Functions Also didn't know this. Yes local state destroys scalability but it is such a convenience sometimes. Will also check this out.