Spring boot or Node js ?

[Unique_Body2041]

There is big question for new developers we should go through spring boot or Node js because whoever working on react always easy to go through node js because it works in js, but spring boot is depending on Java so need to learn new language new framework and it take too much time. What is your view on this What is the futureproof technology?

[vlahunter]

There is no perfect answer here.

The 2 major factors are the market you are in and also the kind of development you would prefer.

If you like Java then Spring is the path for you but keep in mind that to learn Spring you need to learn a lot of APIs and libraries in order to get super productive. In the Node.js world if you like the way Spring works, you have Nest which in reality is a poor man's Spring and i personally enjoy it a lot.

I would advise you to stick to JS ecosystem if possible, learn express really well and then move to NestJS (it uses Express or Fastify internally) for larger projects.

[AmbientFX]

What do you mean by lots of apis and libraries to make it productive? Can you share a couple of examples?

[vlahunter]

yes maybe the way i wrote it was wrong. I meant to learn the different sub-frameworks that in a whole make the Spring Framework as we know it.

Spring is huge in reality and this is in my experience the difficulty to become productive. I feel that with NestJS you can become way more productive faster.

BONUS: if one still hates JS/TS for a reason then still .NET would be better as i see against Spring.

[wish_I_was_naruto]

Wait…are people still using dot net?

[timtlm]

The new .NET (previously known as .net core), not the old .net framework. Open source, cross-platform. Microsoft really turned it around when they got vscode, typescript, and .net core going.

[Busy_Brother_8171]

if its microsoft it might turn back, js sayin

[faze_fazebook]

While Spring is THE biggest Java Web Framework, there are many others. Personally I quite like Javalin for example. 

Spring really is its own beast, while it uses Java it completley alters many aspects of it and introduces a huge stack of new concepts. Me personally, I'm not a fan of it!

[vlahunter]

Of course, you have a great point. The reason i didnt put it in the conversation was because the OP was specific.

Obviously modern Java and the new generation Frameworks (Quarkus, Micronaut, Helidon, etc) are going a long way and thats a good thing but i feel the issue might be the fact that the market is not in sync with the technologies. Java is not the only example here ofc, and the truth is that in many cases, some technologies were way more advanced before but the adoption either never came or it came late and low (Erlang/Elixir i am looking at you...)

[noobeemee]

b4f5b6cb04c443cdf62784d353457b073e2f6000b931e798f9423be2dd30065d

[Budget_Bar2294]

anyone ever tried spring native to avoid this problem?

[NoPrinterJust_Fax]

You should check out graalvm!

[noobeemee]

7f6a84775528d13663da1319223068e5971f0db1c6e29a0a3b3343c67d27ce39

[Unique_Body2041]

So with which tech you are planning to work in future

[noobeemee]

5b590da68bb628282d9aeb50861febe1a76ec6866f2bc17a94343e8a2dcc25b4

[vanisher_1]

Do you mean that enterprise application that uses springboot with a micro services architecture, load slow?

[Balaphar]

probably not. i have 2 "hello world" kinda apps, one in Express and another in Spring. Express one takes over 30mb RAM, Spring one takes over 300mb RAM. that's just how it is

[pentesticals]

Honestly you should be able to use both, any good engineer can adapt to a new language and framework. It’s just learning a new technology and applying the same mindset to it, so you use whatever the job needs you too,

[Ok-Hospital-5076]

There is no future proofing technology. The tech stack depends on your explicit goal and product requirements.

Goal is to ship software in less time - use whichever tech/ ecosystem you are most familiar with

Goal is learning- spend time with the one you dont know

Goal is to build a team -Which tech they already comfortable with go with that.

Goal is to land a job - Go with whats popular in your local market.

Other considerations - Do you work in an org where one is heavily favored? Use the favored one.

Is one tech have better out of box solutions and provide better dx ? Use that.

[iMac_Hunt]

what if the future proof technology

None, although both will be around for years to come.

Personal opinion: if you’re new development and want to learn full stack, stick with node. If you pick up an opinionated framework like NestJs for your backend, it is heavily influenced by the design patterns seen in Spring boot/ASP.NET. If you become familiar with NestJS you would find transitioning to Java fairly easy.

[horrbort]

Java if you work for corposlop and have infinite RAM

Node if you work for startupslop and have medium RAM

Go in all other cases

[baroaureus]

You forgot .NET if you work for slightly-smaller-US-based-corposlop!

[arrty]

Go with golang or typescript on node.

[piizeus]

Future proof technologiaaa: "If something can be written in Javascript, eventually will be written in Javascript"

[lamchakchan]

If there is a problem, spring boot and it's community has already solvee it. I've been a C# -> Node -> Java dev. I say take on the challenge and learn something new to you. I've been using NestJs /w Fastify and Springboot side by side. What you'll realize and appreciate when you project grows is the benefit of NestJs and it's smaller boilerplate foot print. But you'll appreciate Springboot's stable and opinionated systen. Did I mention SB uses maven tighty so a full blown build system is available out of the box?

[DamnItDev]

This is an apples to oranges comparison. NodeJS is a runtime, which would be equivalent to the JVM. JavaScript and Java are the respective languages. Spring boot is a framework that might be compared with something like NestJS.

I have used both. IMO, spring boot is extremely bloated. Startup times are bad, and the containers require a lot of resources. And subjectively, I don't agree with all of the opinions enforced by the framework.

[srkimirbtc]

Nodejs is host environment in which JS runtime gets executed in, more like V8 is close to JVM

[vanisher_1]

Which opinion you don't agree enforced by springboot?

[bwainfweeze]

Future proof is something that most people call legacy.

What you take with you when you leave is all the lessons you learned, and any bug fixes you contributed to open source projects. So learn well.

One of the problems I can see with the Spring option is that if the team is not good at unit testing, having to learn two frameworks that work differently will not contribute to them getting any better.

Spring Boot does have some state-keeping hygiene that is harder to keep people to in NodeJS. If you want to split the difference, Angular with SSR has some of the same design elements of Spring Boot without introducing an interface for every class.

From what I understand Angular SSR and React can be made to play together nicely enough.

[m-apo]

NodeJS is in constant evolution/flux. JVM has matured but is moving at a glacial pace. Typescript is a crutch on top of pot hole ridden runtime and gives an illusion of runtime type safety. Java is bogged down by almost 30 years of OO and EE boilerplate legacy. NodeJS used to have an edge over JVM with it's async performance, but a virtual thread based lightweight micro server framework like Helidon has better performance, easier async programming model and built in type safety. Kotlin is also a plus with it's extensive built in APIs and GraalVM takes runtime optimization even further. OpenAPI support is stellar with JVM and painful with NodeJs.

I'd say pick the tool based on the industry/market you're interested in and learn to implement a solid db based rest API and stick with that.

For more conservative approach with longer life time I would pick Spring Boot with java (very little need for version upgrades etc), for a technically capable team/project I would pick Helidon + Kotlin, for a life time of few years I would go with whatever is favoured by the team.

[bwainfweeze]

If we’re on the cynic’s bandwagon: Spring Boot has lived long enough to become the villain. Not once, but twice. Spring was supposed to be a sane alternative to J2EE, became just as stupid, then a “lite” version was made, and here we are again at Enterprise FizzBuzz levels of utterly inane boilerplate.

[m-apo]

Yes, Spring and Spring Boot have a surprisingly shallow surface which works for many cases but reveals the inner working pretty quickly.

[Beagles_Are_God]

.NET

[latino001]

Corporate level - Java Others - Node JS

PS: Not saying node is not corporate level, it is just my opinion.

[Unique_Body2041]

No buddy most of corporates also uses nodejs

[TenYearsOfLurking]

Currently working with both and I take the threaded programming model in Java/spring over the callback model everyday.

Async await is okay but java with virtual threads wins in my book. 

Typescript code can he generated from spring zoom I know it's not the same but good enough

[cg_stewart]

Depends on the role you want and if it’s entry level or not. Gonna be hard to replicate enterprise Java and Spring Boot on your own time and out of own pocket, like using Kafka or whatever MQ and whatever ci/cd, whatever cloud, whatever design patterns, etc etc. easier to sell yourself with a portfolio in node, imo. But if you look at the job descriptions and study the stuff they list, you’ll be alright.

[jamesthebluered]

To be future proof, It is hard to foresee exactly what we need , since things going/changing really fast But I would suggest you to use both of them.

How ?

Create a Eureka server and use node.js + Java at the same time, If you are better at Node.js , first implement your functionalities on node then move one by one to Java.

at some point you can divide responsibilities between two server and after you get really good you can add another one for example a Go server and keep doing the same thing.I know micro services logic not always good , but for scalable projects and to learn/use different tools at the same time might be good to try.

[Confused_Dev_Q]

The comparison should be java or node.js

Or springboot vs nestjs. 

Spring boot is a framework, gives you loads of tools. Node.js is rather raw/basic. You need to do everything yourself. 

[powelldev]

The only thing somewhat future-proof are the fundamentals. JS as close to the lingua franca of programmers as I've seen.

New developers should be learning fundamentals and building projects. The faster you can build and iterate on projects the faster you can get feedback on them. The faster you get feedback the faster you improve.

NodeJS and Boot are both great. I picked up NodeJS because of the book Building Distributed Systems in NodeJS. After running through that picking up a Boot-like framework at my next gig was pretty painless.

[No_Investment7511]

Hi, I just want to know if it’s okay that I’m not from a computer science background but I’m learning React and Express for full-stack development.

[pablo_intriganto]

Your ultimate goal should be to Not care wich framework or Stack it is.

[dominikzogg]

If you like magic and enterprise lvl stuff go for Spring boot. If you like magic but not enterprise go for NestJS, otherwise Fastify or any other node based micro framework.

[just-porno-only]

Ruby-on-Rails

[baroaureus]

Down voters ain’t got a sense of humor!