Hacker News new | ask | show | jobs
by blzaugg 2240 days ago
I'd like to see some general best practices/architecture. Something that would fit a large range of web applications, not just the one I'm making.

For context, below are some details of what I plan to make.

This web application will have: - user provided content - login/sign-up - email notifications (sign-up, user comments, etc) - limited number of users at the beginning (less than 100 per day). But I want it architected in a way that allows me to scale up when the time comes. - Standard web application security patterns - Standard web application performance patterns (load balancers, containers, CDNs, etc) - Secrets will be stored in Vault (or similar)

My planned full-stack is: - Vue - Vuetify - PWA - SSR - Apollo GraphQL + Hasura + PostgreSQL - Node or Python

2 comments

I agree, this is somewhat standard. Maybe I'll do a quick video on the architecture to use for something like that.

BTW I created something similar and wrote about it here: https://medium.com/@budilov/create-a-serverless-data-lake-on...

Although I also created a Data Lake so there's additional info there.

This is great