Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Boilerplate

github.com

Post reply on HN
Print view View original

51–60 of 62 posts

Re: AWS Boilerplate

#51

Post by jlj »

whalesalad wrote: post #27
jlj wrote: post #22

AWS Amplify is in a similar space. It supports several frameworks and the development workflows and infrastructure management are built in to the project. https://aws.amazon.com/amplify/

I urge fellow readers to try and plan out your entire app arch on Amplify before committing to it. I have found it to be a pain in the ass because it tends to want to do everything for you leaving assets/buckets/things like `aws-amplify-23094139-85-3981759387593745983475-us-east-experiment-project` all over your account. I have been using AWS for over 10 years, so I tend to like to keep a clean house and name most of…

I've found that creating a new isolated AWS account works well for this type of issue. In AWS organizations you can setup the new account using "+" in your email address, such as {your-email}+experiment-project@example.com. Then if you need to burn down everything and start over there is no impact or risk, and naming conventions are less relevant because everything in your "...+-example-project@" account is related to that one project.

Re: AWS Boilerplate

#52

Post by sneak »

nixgeek wrote: post #24

Initial reaction to seeing HN showing me “AWS Boilerplate (github.com)” was I thought AWS had launched a new service and it was potentially open source. Please consider renaming to something like ‘Boilerplate for AWS’ since it would avoid confusion that this is something official from AWS, and because such a name is less likely to cause trademark issues per the AWS Trademark Guidelines. https://aws.amazon.com/tradema…

I think the same result could be achieved by simply lowercasing the ‘b’.

Re: AWS Boilerplate

#53

Post by jjeaff »

freehunter wrote: post #18
williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

This is why I love opinionated frameworks, why I love hand-holding tutorials, why I love abstractions. I don’t like code. I don’t like writing it, I don’t like reading it, I don’t like thinking about it. A mechanic doesn’t love his crescent wrench, he loves working on engines. The wrench is just a tool. What I enjoy is the final product and seeing a project come together as time goes on. “The right tool for the job”…

If mechanics didn't love their wrenches, companies like Snap-on tools wouldn't exist. Where you get the same thing as a good tool at a big box store, but for 5x the price.

Re: AWS Boilerplate

#54

Post by sunilkumarc »

dang wrote: post #45
sunilkumarc wrote: post #23

Nice. This boilerplate can really help people get started quickly. Well done :) On a different note, recently I was looking to learn AWS concepts through online courses. After so much of research I finally found this e-book on Gumroad which is written by Daniel Vassallo who has worked in AWS team for 10+ years. I found this e-book very helpful as a beginner. This book covers most of the topics that you need to learn…

Your repeated promotion of this book in HN comments has crossed into spamming, and we're getting complaints about it, so please stop.

Sorry. I thought promotion of affiliate books was okay here. I'll stop it :)

Re: AWS Boilerplate

#55

Post by moltar »

My dream is to build something like this but in TypeScript, full stack. Using CDK for deployments, but also a really tight integration with higher order components. E.g. define a lambda handler and it automatically wires CDK code.

I guess kinda like serverless framework, but much less YAML and much more actual code.

Re: AWS Boilerplate

#56

Post by williamdclt »

corytheboyd wrote: post #35
williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

I have never worked for such an agency, but I actually find value in setting up some of the infrastructure from scratch, at least on the application side. It’s a time to dig into the latest versions of each component, or apply learning you wish you could have on other projects but things got too big to make large architectural changes. It costs a few days, but you’re laying down what should be the forever foundation,…

The project generator became a core part of our business (and a sales argument, actually), so it was maintained to be up-to-date. It's the implementation of what we collectively knew to be best practices: you don't always have time or knowledge to set up each individual component of a project.

If there's a later version of a component or you want to apply learning... contribute back to the project generator, to ensure other projects benefit from it

The only value we lost was the experience a dev gets setting up the infra from scratch. It is a consequent loss, but we deemed it very worth it (and retrospectively, I think it was)

Re: AWS Boilerplate

#57

Post by williamdclt »

whalesalad wrote: post #26
williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

For folks who want a tool to help them accomplish this, I have heard good things about cookiecutter: https://github.com/cookiecutter/cookiecutter

It was one of the options I looked into, yes :) IIRC it's python-only, so didn't fit the bill. We ended up using Handlebars templates, and Plop (https://plopjs.com/) for prompts and the generation logic. It was lightweight and extensible, worked great

Re: AWS Boilerplate

#58

Post by fwang »

moltar wrote: post #55

My dream is to build something like this but in TypeScript, full stack. Using CDK for deployments, but also a really tight integration with higher order components. E.g. define a lambda handler and it automatically wires CDK code. I guess kinda like serverless framework, but much less YAML and much more actual code.

Yeah, we often recommend using Serverless Framework and AWS CDK together. Serverless's strength is working with Lambda and API Gateway, but writing YAML for the rest of the resources is very cumbersome. So a good pattern here is to use CDK for the rest of your infrastructure, and Serverless for your Lambda functions.

In fact, we created a tool to do exactly this - Serverless Stack Toolkit (SST), which allows you to combine CDK and Serverless Framework - https://github.com/serverless-stack/serverless-stack

So you can do `sls deploy --stage dev` and `sst deploy --stage dev`.

Re: AWS Boilerplate

#59

Post by moltar »

fwang wrote: post #58
moltar wrote: post #55

My dream is to build something like this but in TypeScript, full stack. Using CDK for deployments, but also a really tight integration with higher order components. E.g. define a lambda handler and it automatically wires CDK code. I guess kinda like serverless framework, but much less YAML and much more actual code.

Yeah, we often recommend using Serverless Framework and AWS CDK together. Serverless's strength is working with Lambda and API Gateway, but writing YAML for the rest of the resources is very cumbersome. So a good pattern here is to use CDK for the rest of your infrastructure, and Serverless for your Lambda functions. In fact, we created a tool to do exactly this - Serverless Stack Toolkit (SST), which allows you to c…

Looks awesome and exactly what I needed. Will sign up tomorrow!

Re: AWS Boilerplate

#60

Post by freehunter »

jjeaff wrote: post #53
freehunter wrote: post #18

Earlier quoted context omitted.

This is why I love opinionated frameworks, why I love hand-holding tutorials, why I love abstractions. I don’t like code. I don’t like writing it, I don’t like reading it, I don’t like thinking about it. A mechanic doesn’t love his crescent wrench, he loves working on engines. The wrench is just a tool. What I enjoy is the final product and seeing a project come together as time goes on. “The right tool for the job”…

If mechanics didn't love their wrenches, companies like Snap-on tools wouldn't exist. Where you get the same thing as a good tool at a big box store, but for 5x the price.

Snap-Ons business model isn’t the high quality of their tools, it’s their financing. I have a mechanic friend who is over $7,000 in debt to Snap On. They’ll finance just about anyone who has a job.
Post reply on HN