Earlier quoted context omitted.
That future is being created, you're probably just less aware of it than you think. Serverlessconf just announced their NYC conference, expected to be the largest yet. If Austin is any indicator, it will be huge. [1] Tim Wagner at AWS likes to spout the stat that billions of financial trades are already being processed per day on AWS Lambda. The "serverless" market is gigantic and growing rapidly. And then there's co…
Oh, I know it exists, and I know tons of people are using it. But like I said, I don't think that the tooling is there right now for mass migration (or anything like it). It's really difficult to test/debug. It's difficult to dianose issues. It's difficult to even set up a "Hello World" API Gateway that uses lambdas. It's painful... as are all new technoligies. I guess what I mean to say is: I look forward when I jus…
Build a Serverless Web Applicaion
31–40 of 152 posts
Re: Build a Serverless Web Applicaion
#32Has anyone used RDS from lambda? Don't want to use Dynamo but perhaps for some key Val store.
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
Re: Build a Serverless Web Applicaion
#33Mostly stoked about serverless because I won't have to deal with grumpy backend devs anymore
Re: Build a Serverless Web Applicaion
#34Mostly stoked about serverless because I won't have to deal with grumpy backend devs anymore
Re: Build a Serverless Web Applicaion
#35Earlier 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".
The future is bare metal IaaS with something non-provider specific that sits on that as that is 100% portable between Cloud/in house. Docker/openstack that sort of thing.
Re: Build a Serverless Web Applicaion
#36I wouldn't be surprised if it achieves a near-monopoly for a while... But I think that eventually more flexible open source solutions will take over. Open platforms like Docker and Kubernetes will likely replace Lambda just as Linux replaced Windows on the server-side.
Re: Build a Serverless Web Applicaion
#37In principle I really like this way of developing, and especially prototyping, but as it stands right now Google is doing a significantly better job with their tools than Amazon. Amazon got the same guts, but their presentation of these tools is horrendous. It's aimed at the highly skilled developers who would get the concepts in a blink, with the only problem that these are the same people who can spin out servers w…
In most cases people are trying to enhance what they already have which means needing access to what is already there.
Re: Build a Serverless Web Applicaion
#38- watchout for latencies (multi-zones apps) time of your lambda functions. - keep your lambda functions warmed up - node has better warmup time than java lambdas (not sure of python) - memory size impact of lambda functions (negligible in most cases) - manage lambda timeouts - dynamodb latencies are negligible - api gateway typically does not introduce latencies - multitenancy challenges with single store of dynamodb
Python and node are both sub-second, compared to Java's 10+ seconds.
Re: Build a Serverless Web Applicaion
#39Has anyone used RDS from lambda? Don't want to use Dynamo but perhaps for some key Val store.
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
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.