Live data from Hacker News

Cloud Programming Simplified: A Berkeley View on Serverless Computing

rise.cs.berkeley.edu

41–43 of 43 posts

Re: Cloud Programming Simplified: A Berkeley View on Serverless Computing

#41
Great paper, I've only gone through about 10% of it, but it offers a lot that the vendor docs and industry talks don't.

Btw, this is David Patterson one of the inventors of RISC fame. Great podcast with him here (mostly about new Tensorflow chip and history): https://softwareengineeringdaily.com/2018/11/07/computer-arc...

Worth noting that he's at Google, but it looks like he had AWS reviewers.

Re: Cloud Programming Simplified: A Berkeley View on Serverless Computing

#42

Earlier quoted context omitted.

But we did, didn't we? How is modern serverless different from shared LAMP hostings of the past?

Shared lamp hosting didn’t give you the security, scalability or isolation that lambda gives you.

The implementation was lacking, but the concept is nearly identical.

Re: Cloud Programming Simplified: A Berkeley View on Serverless Computing

#43
post #17

Earlier quoted context omitted.

The interface between Lambda and your business logic is usually very thin so in case of simple REST APIs migrating from platform (as long as the target platform has a compatible language runtime) to another or to be executed in a web app framework is rather easy. Serverless applications' reliance on other proprietary services like Cognito, DynamoDB etc is another thing however...

The problem is also that Lambda works really poorly with anything that is NOT Cognito and DynamoDB. For example, we were using some CouchBase we deployed ourselves - however, that meant that the Lambda now had a network interface in a private subnet, and start times skyrocketed, especially for concurrent access. When we also started doing our own authentication with yet another Lambda, request times for cold lambdas…

AWS is solving cold start times for VPC Lambda, they announced it at re:invent.
Post reply on HN