undefined | Better HN

0 pointsmaxcan3y ago0 comments

Data: Postgres & Hasura (for me Hasura is the goldilocks level of abstraction - lets me skip writing CRUD handlers, but doesn't get in the way either when I need to do something complex).

Frontend: TypeScript, React, apollo client, graphql-code-generator, tailwind

Backend Logic: Lambda functions written in TS, packaged with serverless.com, but deployed with Terraform

CI: GH Actions

Deployment: AWS via Terraform. One account per environment under an umbrella org.

Because I've used this stack so many times I can get a "shovel ready" foundation going in minutes with a skeleton that I've been iterating on.

0 comments

2 comments · 1 top-level

0xblinq3y ago· 1 in thread

And god protects us if some day you leave the project and somebody else has to come and understand these setups.

I bet you know this very well and you’re very productive with this, but just imagine the next person having to pick it up.

That’s where full stack batteries included frameworks shine… you know what to expect and how things fit together, you just need to figure out the business logic.

maxcanOP3y ago

Besides Hasura, every element of the stack is either the dominant tool in the market or one of the most dominant tools in the market (terraform). Hasura is pretty thin and not too hard to pick up.

Please enlighten me as to which “batteries included frameworks” have the market dominance of AWS, React, TypeScript, and Terraform?

j / k navigate · click thread line to collapse