[baoluofu]

Both API and web app served out of AWS lambda/API Gateway/Cloudfront. Back office app served from S3.

- React and next.js for the web app.

- Node.js & express for the API.

- React-admin for the back office.

- Postgres for the DB.

The biggest benefit to me of the above stack is running it out of AWS lambda. Pay only for what actually gets used, and more importantly it will scale to any sudden surge in customers without any effort on my part.

[midrus]

Hi, honest questions of things I struggled a lot with when tried to build applications with his stack:

What do you use for accessing the database or as ORM, etc?

How do you do validations server side and show error messages to the user?

How do you do i18n in general, and also related to the previous question (error messages)

Do you use any CMS? How do you explore your data?

How do you do background jobs?

How do you do migrations?

How do you do authentication and permissions?

All these things are what drove me back to Django. I wonder how people solve this without reinventing the wheel or having to write and test a ton of glue code. I wonder if I'm missing something or I'm just too lazy or not good enough (I'm not trolling, just genuine concerns)

[robertlagrant]

Presumably Next answers some of those, and things like background jobs must just be lambdas as well?

[midrus]

Can you point me to the docs or those solutions? I haven't found them when I looked for. Of course there are tons of examples integrating with third party libraries, etc...but tying everything together is what worries me.