Guide to Serverless Architecture
simform.com
Guide to Serverless Architecture
1–10 of 105 posts
Re: Guide to Serverless Architecture
#2> Drawback of Serverless: Vendor lock-in, statelessness, local testing, cold/warm start perf, security, deployment, execution, monitoring, remote testing, debugging.
Excuse me? Let's use lambda for what it was meant to do, not replace your entire stack.
Re: Guide to Serverless Architecture
#3CGI scripts with a new name. Lambda and the like are interesting but any system is a composable set of components.
You can say the same about Object oriented programming or func programming. separation of concerns but on the network. Server functions arent a panecea cause you still have to manage all the other pieces.
An elegant thing would be your entire app is in that single lambda but without state there goes your db. even so, people cant resist taking something and adding and adding more to it.
Re: Guide to Serverless Architecture
#4> Drawback of Serverless: Vendor lock-in, statelessness, local testing, cold/warm start perf, security, deployment, execution, monitoring, remote testing, debugging. Excuse me? Let's use lambda for what it was meant to do, not replace your entire stack.
But 'serverless' has a much nicer ring to it than 'serverfewer'...
Re: Guide to Serverless Architecture
#5CGI scripts with a new name. Lambda and the like are interesting but any system is a composable set of components. You can say the same about Object oriented programming or func programming. separation of concerns but on the network. Server functions arent a panecea cause you still have to manage all the other pieces. An elegant thing would be your entire app is in that single lambda but without state there goes your…
More like CGI scripts with a loadbalancer that promises to run your application on a host with enough memory within at most 600ms. That solves an actual problem with CGI scripts, but I really would love to see more tiers with lower latency brackets, sub 10 milisecond should be doable for certain lambdas and costs.
Re: Guide to Serverless Architecture
#6It's redirecting to their homepage. Am I missing something?
Re: Guide to Serverless Architecture
#7It's redirecting to their homepage. Am I missing something?
You might want to use a VPN, sometimes organizations enable geo filters.
Re: Guide to Serverless Architecture
#8Only Google and Amazon exist in this write-up? This is not a guide, more an intro.
Re: Guide to Serverless Architecture
#9The phrase that Amazon used when launching lambda was 'deploy code not servers'. To me this sums up what 'serverless' means. It means the developer doesn't have to worry about servers in any way.
With AWS Lambda/API Gateway (and arguably with Google App Engine before it) you take away the toil of having to:
* Manage/deploy servers
* Monitor/maintain/upgrade servers
* Figuring out tools to deploy your app to your server
* Scaling an app globally.
* Coping with outages in a data-centre/availability
* Worry about load-balancing & scaling infrastructureRe: Guide to Serverless Architecture
#10> grouping a bundle of functions together behind an API gateway, you’ve created a microservice
Always beats me why people don't warn the readers about the almost impossible nature of logging and monitoring such systems :/