Live data from Hacker News

Build a Serverless Web Applicaion

aws.amazon.com

41–50 of 152 posts

Re: Build a Serverless Web Applicaion

#41
Is anyone else slightly peeved by the popularity of this misnomer?

If you are paying for servers, your app isn't serverless. Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.

Re: Build a Serverless Web Applicaion

#42
post #41

Is anyone else slightly peeved by the popularity of this misnomer? If you are paying for servers , your app isn't serverless . Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.

It actually has lead to confusion before when I assumed that someone I was talking to knew what this usage of "serverless" meant. And it was only 15 minutes of talking that we realized our conversation had wildly diverged and neither side knew it.

Re: Build a Serverless Web Applicaion

#43
post #41

Is anyone else slightly peeved by the popularity of this misnomer? If you are paying for servers , your app isn't serverless . Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.

Not just peeved, but confused.

"With serverless computing, your application still runs on servers"

So it's not serverless? Why are you calling it serverless?

Re: Build a Serverless Web Applicaion

#44
post #39

Earlier quoted context omitted.

Yep, very easy with JDBC + APIs like JOOQ. The "interesting" part is how to secure user credentials to login to the RDS instance, and manage connection pools etc, but it's not that difficult

> The "interesting" part is how to secure user credentials to login to the RDS instance, and manage connection pools etc, but it's not that difficult You can run your RDS instances and your Lambda's in the same private VPC. It doesn't secure your credentials per se, but it does prevent anyone else from accessing your database with Lambda.

The "problem" with putting Lambdas into a private VPC is that then you need to do NAT, which means permanent infrastructure (NAT gateways, failover, scaling...). It can be done but there are more headaches than with a pure serverless solution. Unless things have changed since the last time I looked at this stuff.

Re: Build a Serverless Web Applicaion

#45
post #39

Earlier quoted context omitted.

Yep, very easy with JDBC + APIs like JOOQ. The "interesting" part is how to secure user credentials to login to the RDS instance, and manage connection pools etc, but it's not that difficult

> The "interesting" part is how to secure user credentials to login to the RDS instance, and manage connection pools etc, but it's not that difficult You can run your RDS instances and your Lambda's in the same private VPC. It doesn't secure your credentials per se, but it does prevent anyone else from accessing your database with Lambda.

Sadly putting Lambdas in your dedicated VPC introduces cold start times of sometimes ~5 seconds. Yes, seconds.

Re: Build a Serverless Web Applicaion

#46
post #41

Is anyone else slightly peeved by the popularity of this misnomer? If you are paying for servers , your app isn't serverless . Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.

The very first time I heard "serverless" I thought P2P, but even though I agree somewhat with what you said, think of it as serverless because you don't have to manage the servers yourself.

Re: Build a Serverless Web Applicaion

#47
post #41

Is anyone else slightly peeved by the popularity of this misnomer? If you are paying for servers , your app isn't serverless . Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.

[deleted]

Re: Build a Serverless Web Applicaion

#48

Earlier quoted context omitted.

AWS is the system architecture of the web, full-stop. Well, a system architecture, alongside Microsoft Azure and Google Cloud. Avoid them at your own peril and detriment to your ability to execute as a business. With the exception of a few masochists, we don't write software in machine code anymore. Same will be said for cloud infrastructure (actually, it's already there). Breathe and accept the future, focus on buil…

Right now I spend $240-600/mo for 192TB of bandwidth. I just used AWS's calculator and they charge $38,876.48/mo for the same thing. I don't subscribe to the theory that this is "the future".

Imagine what would happen to AWS if more companies practiced the Amazon Leadership Principles [0]

Frugality

Accomplish more with less. Constraints breed resourcefulness, self-sufficiency and invention. There are no extra points for growing headcount, budget size or fixed expense.

Because you know Leadership Principles aren’t just a pretty inspirational wall hanging.

[0]https://www.amazon.jobs/principles

Re: Build a Serverless Web Applicaion

#50
post #41

Is anyone else slightly peeved by the popularity of this misnomer? If you are paying for servers , your app isn't serverless . Real serverless to me means decentralized p2p and offline apps. I also consider p2p-routed apps with centralized control serverless as long as they continue to function in a read-only state when the control server is down.

Serverless refers to your workflow & division of responsibility, not the literal stack. Personally I think there are enough things to be peeved about in the world without adding this.
Post reply on HN