AWS Boilerplate
github.com
AWS Boilerplate
1–10 of 62 posts
Re: AWS Boilerplate
#2Re: AWS Boilerplate
#3Re: AWS Boilerplate
#4This is what happens when someone hears the phrase "one size fits all" and immediately thinks to themself, "Hey, I'M one size!"
Re: AWS Boilerplate
#5Anyone else feel like AWS's primary goal isn't actually to make money but to put us all out of a job, but it doesn't quite know how to do so
Re: AWS Boilerplate
#6Re: AWS Boilerplate
#7This is what happens when someone hears the phrase "one size fits all" and immediately thinks to themself, "Hey, I'M one size!"
It's a helpful, opinionated boilerplate.
Re: AWS Boilerplate
#8Re: AWS Boilerplate
#9Anyone else feel like AWS's primary goal isn't actually to make money but to put us all out of a job, but it doesn't quite know how to do so
Not just technically, but in terms of their mental model on how to build and deploy applications. Over time, "just use AWS" becomes the defacto "how do I build this?" answer until nobody really knows how to build and deploy an application without them.
It's damn clever.
Re: AWS Boilerplate
#10“Backend” is a Django application - but not mentioned in the README, for example.
Also, what AWS services are being utilized? The Serverless stuff deploys to Lambda... that can be inferred, but the rest of it?