Hacker News Reader

Hacker News

Comment by k__ | Hacker News Reader

Parent Full thread

k__

"Limited Programming Languages"

AWS Lambda can run all programming languages via layers.

Cloudflare Workers can run all programming languages that compile to WebAssembly.

"Vendor Lock"

True, but being locked into Kubetnetes isn't a cakewalk either.

"Performance"

Cold-starts aren't a thing for Cloudflare Workers and can be mitigated for AWS Lambda. AppSync and API Gateway don't even have them if you directly integrate with AWS services.

"You Can't Run Entire Applications"

You can and it has been done multiple times. Sure, you shouldn't blindly build everything with Lambda and API-Gateway without measuring. But many services, especially Cloudflare Workers are quite cheap.

View on HN

K8s can go almost anywhere any time with fairly minimal ramp. With the frequency I am hearing about AWS billing disputes these days it's probably best to not seal the keys to your kingdom in their service.

The problem is getting K8s to the point that it can go almost anywhere.

Eh? I was able to go from a docker image to live and 0 downtime deploys in a few hours?

But how many hours/days/years did it take you to learn how all the parts move before you became capable of setting something like that up within a few hours?

Anecdotally, stories of businesses abandoning entire cloud automation projects because they wasted weeks and never had anything to show from it don't seem unusual, so evidently a considerable amount of knowledge and skill is required to get value out of these tools.

None really? I don’t consider myself the worsts best Sysadmin, but the hard part was making an app docker. Making a docker k8s was easy.

This.

I used K8s and serverless tech and while serverless wasn't as simple as some evangelists try to sell it, it was at least a magnitude simpler than K8s.

Even managed K8s, which removed most of the admin plane work with nodes, was still significantly more work to get up and running.

My worry is less about getting it set up to run a container and more about securing it, monitoring it and being able to respond should things go wrong.

Sure, everything can be done serverless with a bunch of workarounds, that's one of the reasons it stalled IMO.

Serverless makes somethings easier and other things harder, so it's advantages over good old fashioned servers are clear cut.

In my experience there are only a few edge-cases that need workarounds and even those get fewer with every release.

Did you mean aren't clear cut? Autocorrect?

Yes, i meant "aren't". Damn you autocorrect!

> AppSync and API Gateway don't even have them if you directly integrate with AWS services.

I was quite impressed when I exposed Kinesis via API Gateway, it just worked, although the Kinesis requirement that data be b64 encoded did require some fiddling about with mapping templates.

People always think serverless mean FaaS, while in fact you should use FaaS only to glue together other serverless services when it's not otherwise possible.

Sure, a container is better than a serverless function in many ways, but the function isn't what the container is competing with.

cloudflare workers has been doing very well for me too. the only problem is it's too tight down to CF

Reply on news.ycombinator.com