Ask HN: CRUD Apps in 2020? What are the current best practices and architectures

Just realizing now, "CRUD app" is almost meaninglessly vague - just means an app that reads & writes data, which is almost every app. Calendar, contacts, email client, image editor, blog, comment section, forum - all CRUD apps, as they focus on reading & writing specific types of data.

But obviously there's a world of difference in interface, usability, aesthetics, performance, good writing, security etc. The CRUD part is the simple part.

I guess there's some spectrum between a dumb unspecialized list of table editors ala phpMyAdmin, versus hyper specialized interfaces like game engines that manipulate scene data, triangle data, player inventory, physics entities etc.

I would still choose the same stack I was using 5 or more years ago. Python (Django or Flask) or Rails with either Postgres or MySQL - whichever your organization is most familiar with. Avoid NoSQL unless you have a very good reason for it but even then Postgres should serve you just fine.

Note that YMMV with the above if adopting serverless.