Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I can't speak for nextKS specifically, but you hit the nail on the head. Monoliths are great for small and medium sized projects.
Gotta Keep It Simple Stupid, and go fast at all costs. Future scaling requirements be damned.
I think there are good test frameworks in JS though. I'm not a JS guy though, so I'm not 100% on it. -
* 18 months later *
Business: we want it to be a mobile app as well. Exactly the same features but has to be an app users can download for Android AND IOS.
Devs with coupled front-back end: oh shit
^I mean you might be alright if you always have big firegaps been the frontend and backend code in the repo around your APIs so new UIs are easier to slot in 🤷 -
@b2plane yeah that's basically the jist of it. Don't scale until you need to scale, because 90% you'll fail before that anyway, and you don't want a complex microservices system to be a reason for it.
if right now you have a separate back end, you have a dualith, not a monolith. Not that there's anything wrong with that. I'm a big fan of separation between front and back ends, but when you have a small team and a smaller budget, you do whatever is fastest. And that's monoliths. -
@lungdart I think the problem with nextJS 13 is beyond monolith vs microservice question. The idea of writing a backend in js isn't very tempting for lot people. So imagine not only having to write the backend in J's, but also being forced to couple it with the front, same codebase. Kind
-
@b2plane it's time for vue!
-
LoL. React is Next.js at this point. Also, you are expected to use next.js along with vercel infrastructure. Vercel will handle all scaling issues for you even though they suffer from outages often.
You probably should watch some talks regarding meta frameworks before jumping in 😂. If you are gonna build an app that is locked behind authentication. Don't use nextjs -
@b2plane you use all 3rd party services for those features. Abuse the heck out of s3, and ship something with RCE built in as a feature, and cash the VC cheques before they know the difference.
-
@b2plane because you're not optimizing for speed!
In all seriousness, there are great open-source self hosted alternatives to saas, and all you have to do is not being afraid of hosting more than one thing.
Personally, I run k8s clusters, and fire everything into them. Costs be damned! I even run k8s at home on my proxmox cluster. -
FWIW, getting to the direct question:
"Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?"
Yes, absolutely you can. Or alternatively, you can compile the whole lot to static assets, host on a platform of your choice, and then just have your frontend call your SB backend directly (you'll just need to set up CORS correctly for this to work.)
How is coupling backend + frontend as a single nextjs app a good idea? What the fuck is this?
What if you have to create new replica sets of a backend because of high load pressure? What about load balancers?? What if i want my backend to be a microservice? How do i unit test the backend if its cluttered with frontend? WTF IS THIS
WHY DID NEXTJS THINK THIS IS A GOOD IDEA AND WHY DO SO MANY DEVS LOVE THIS IDEA AND GLORIFY NEXTJS?
Nextjs seems like the type of framework that was built by a frontend web developer who just refuses to learn backend technology at all costs.
---
its been a few hours and the concept of nextjs is bending my mind rn. I thought nextjs is just another frontend framework. A react killer. Only to find out its both a backend + frontend framework.
Cluttering backend stuff into frontend is gonna get messy no matter how much you try to modularize the code. Am i lost or am i right???
---
Scratching my head over nextjs. Looks like a great framework for small-mid project but definitely not large project. The more shit the project needs the more messy shit become. Angular has modularized all of this in separate folders -- components services guards interceptors (now new stuff coming called Signals) etc. All of it is separated in individual folders and kept frontend-only. Simple enough. No backend clutter
---
Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?
Am i insane here
rant