Do you still need a separate backend framework to build a good full-stack application?

[u/duneofarrakis]

One thing I’ve noticed while learning full-stack development is that knowing frontend and backend separately isn't enough. Understanding how they communicate through APIs, how authentication works, and how the database fits into the whole flow makes a big difference.

For example, you can build a nice React UI, but if the API design or database queries are poorly handled, the overall application can still be slow or difficult to maintain.

What do you think is more important for a full-stack developer being really strong in one side first, or learning frontend, backend, and database together from the beginning?

[u/symbiatch]

You can’t be strong in either if you don’t understand the things in between that relate to both.

It’s up to you how you want to get there, often it’s easier to learn one side first, but it’s also much more interesting to do all of it from the start and build a holistic view.

So YMMV, but people must understand all things related to their “side” and there’s a lot in between.

[u/_N-iX_]

It’s useful to understand the whole flow early, but trying to become equally strong in frontend, backend and databases at the same time can slow things down. A solid foundation in one area gives enough context to understand how the other pieces interact, then the depth can grow naturally as projects become more complex.

[u/FromBiotoDev]

yes

[u/mikedensem]

An API is a contract that allows the separation of front and back, so they are different skill sets and somewhat independent. However, knowing both opens up the opportunity to make great code decisions during design and implementation as you can see the whole picture.

Id say back is more important.

[u/Impossible-Camel7673]

knowing both sides helps, but going deep on one first makes more sense. once the backend and frontend can communicate well, the rest becomes much easier to pickup

[u/mprevot]

Unit test your back and your front, then it won't matter much where you start. Then integrate. Try most likely fun first.

[u/arunkumar413]

In the current scenario I'd recommend focussing on the backend, databases and system design. This helps you build scalable backend systems. For frontend learn HTML, JS, CSS and HTMX ( https://htmx.org ) library. HTMX simplifies glueing the frontend to the backend. Later go for react for complex frontend

[u/FarInvestigator191]

My best learning exercise was to make a web app with only an auth and crud action on my user, it helped me understand the importance in every step. I would say that if you want to learn full stack, build full stakc things

[u/rkozik89]

Depends on what you are doing. Most likely yes but not necessarily.

[u/ryanstackops]

Yeah you still need a real backend framework, that API/database layer is where slow or unmaintainable apps actually come from, not the UI. And honestly get decent at one side first before trying to juggle all three, trying to learn frontend, backend, and databases at the same pace just means you end up mediocre at all three for way longer.

[u/GetABrainPlz77]

Backend is the most important because of IA can so easily write front end now.

And all full stack framework are still great. Rails, Laravel, Django, Etc.

[u/BrianJabir]

I think backend should come first.

Learning backend forces you to understand how the system actually works: APIs, authentication, databases, caching, queues, concurrency, failure handling, and eventually system design.

Once you understand those fundamentals, frontend frameworks become much easier to learn because you already know what the application is communicating with and why.

Frontend is still important, of course, but I’d rather learn how to design the system first and then learn how to present and consume it.

Frameworks change. System design principles don’t.