DEV Community

loading...

Ask Dev: Full Stack app or JS Frontend powered by API backend?

noncototient profile image Bo ・1 min read

Hey devs!

I am looking to start a new side project, for which I now have a clear idea of what it needs to do, some nice designs and a fitting market I think. I am excited to get started, but I want to decide on the architecture.

In the past I have built many web apps using different technologies, and lately I've been using Laravel with VueJS and absolutely loving the speed and dev experience. Highly recommended.

However, I cannot ignore the awesomeness of universal/progressive web applications. Mainly, I am looking at NuxtJS powered by Laravel API.

The reason why I am writing this is because I am looking for other good reasons to go with NuxtJS + API backend route. Has anyone done this before and seen benefits or is it just hype? Any other good reasons apart from having offline page and ability to install the app?

Discussion (2)

pic
Editor guide
Collapse
evanrblack profile image
Evan Black • Edited

I would say that if the features and design are well set up, then having this separation can work very well, especially if you can treat your API like one that is depended upon by others.

However, for more exploratory development, I find the separation between the two can lead to some increase in maintenance work and context switching. Granted, this view comes from experience working with multiple microservices that aren't maintained quite like public apis. So sometimes delivery of features can feel like you're hopping through a few more hoops than most would prefer.

Collapse
noncototient profile image
Bo Author

I guess this is up to me still 😂