Hacker News Reader

Comment by ManuelKiessling | Hacker News Reader

Here is an extensive step-by-step tutorial which describes in detail how to create and deploy a React-based web app frontend using TypeScript and Redux Toolkit on top of a Node.js based AWS Lambda backend with a DynamoDB database, connect and integrate them through API Gateway and CloudFront, and explains how to codify and automate the required cloud infrastructure and deployment process using Terraform.

The resulting architecture does not require any CORS requests, too:

https://manuel.kiessling.net/2021/05/02/tutorial-react-singl...

View on HN

> Here is an extensive step-by-step tutorial which describes in detail how to create and deploy a React-based web app frontend using TypeScript and Redux Toolkit on top of a Node.js based AWS Lambda backend with a DynamoDB database, connect and integrate them through API Gateway and CloudFront, and explains how to codify and automate the required cloud infrastructure and deployment process using Terraform.

I think it's time we take a step back and address this insane complexity required to send HTML documents to users...

Im not sure if its to deploy a blog or a satellite.

That's a mouthful.

I've read that sentence three times and still were not sure if it's meant as a joke or not.

It’s not – I like to summarize my tutorials comprehensively. I am not a native speaker though; I apologize if the sentence isn’t structured correctly or sounds inelegant. Corrections welcome.

I guess it's just the mind-bogglingly huge number of components involved to display HTML to someone :)

That is absolutely true in some sense - then again, it is one solution where you start with a decent architecture that can grow and is scalable at linear, and very low, costs.

If you were to really only deliver some HTML, it's overkill. For this reason, my blog is hosted with an old-school 90s-style FTP-backed "webspace" provider.

But the architecture described is used to develop-build-deploy a full-flegded web-based application, with a persistence layer for user data and a potentially complex user-interface.

And for this, having a sound architecture and tech-stack where you do not need to care about low-level server issues is, while certainly not a silver bullet, quite a productive experience.

Oh, your language is perfectly fine. It's just that your article description reveals a sad truth about modern web technologies: it's a tangled mess.

Highly complicated jacked up messes that you can't explain to your customers...and they don't care.

That’s frontend for you.

I don't think I'm a fan of CV development...

I hope it's clear that the reference to CVDD is tongue-in-cheek.

Reply on news.ycombinator.com