Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Ask HN: "Modern” Web App Development
13 points by Zababa on Jan 6, 2022 | hide | past | favorite | 2 comments
The last time I did web development from scratch for a frontend-heavy app (think unbundling Excel), the way of doing it was with a frontend in React/Angular/Vue/etc, and a backend REST API in anything. It seems like things have changed a lot, and I'm wondering how I could learn about that and evaluate the different approaches. Nowadays I hear people talking about their frontend framework (React, lots of Next, things like that) and that's bascially it. A few questions:

- How do you handle authn/authz? Do you use auth providers? Who are they, and what are the tradeoffs? Do you deploy yourself an auth API? Which one do people use?

- How do you handle persistance? With database providers, like Firebase/FaunaDB? How's testing?

- Do people just don't write backend anymore? I hear a lot about lambda functions, which seems great for one-off jobs (send an email, process an order), but I don't imagine that people write all of their backend with it. Are backend not a thing anymore?

- If that's the case, what are the tradeoffs compared to the "old" way of doing it, and the even older (server-side rendered HTML with lots of JS)? Do you gain development speed? Maybe you write more code specific to your "problem" and less plumbing that everyone needs? Would you consider this the best approach to develop a frontend-heavy app in 2022?

- How do you learn about all that? Read news often? Are there people making comprehensive reports/tech radars of what's used and how well it works? Are there good books on the subject? Blogs? Podcasts, videos?



It is still very common to have an application server that handles the M and the C in MVC, using frameworks like Ruby on Rails or an equivalent in node/python/whatever.

Next and other SSR JS tools are great and have gained a lot of popularity, but there is still lots of opportunity doing basic front-end (JS) and backend (API and database) development.

Things are evolving, but basic solutions that just work and are simple and easy to understand have a tremendous amount of value in my opinion.


Thanks, but that's not really what I'm asking about here. I know about the more traditional way to do things, and that's what I do daily. What I'm asking about is how the "new stuff" works and how to learn about it. It's sometimes hard to know the tradeoffs involved with only an external point of view, especially when most of the discussion is heavily polarized like here.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: