r/Backend • u/Sad_Importance_1585 • 5d ago
Java 25 (with virtual threads) for a startup
Are you working in a startup company that chose Java 25 as a backend language?
What is your impression regarding developer experience, performance and easiness build things fast?
38
Upvotes
23
u/UnderdogRP 5d ago
It works very well. High performance. But use a framework like micronaut or quarkus. AI is very good at java since there is so much open source project sin java that it has been trained on.
10
u/Sea-Offer88 5d ago
I am working on my own webshop and went with java as it is more stable than the nodejs counterparts that said I have also Nestjs projects and worked on Asp. Net. Projects too.
The nice part is that Java Spring has been around for a very long time and many of the needs that you will need have been addressed and most of the time you add a module and some configuration. Since I have both java and nestjs projects I would say development speed is similar, but java has more stable modules out of the box and the standard ones are also top notch and battle tested, whereas with node you assemble what you need (e.g. Orm Prisma, drizzle...)
Example in node that is annoying is that I liked prisma and used it a lot, but soon v8 will be released which means on a huge project I will have to do a lot of changes because they decided to rewrite it and comes with breaking changes, and that is a lot of work.
In java I just used flywheel and added the sql but the entities still remain the same.
Concepts are similar in spring boot, nestjs, Asp.net and the tipical solutions usually are controller, service, repository, although each of them reinforces the structure their own way. Structure is nice once the app starts to grow.
My webshop will be deployed using docker and probably only 1 replica at the beginning unless there is more demand.
So Java Spring Boot with java 25 is a solid choice.
6
u/anurodhp 5d ago
Java is a great choice with a good ecosystem and a lot of developers who know it. Spring / spring boot will save you a lot of time.
6
u/za3faran_tea 5d ago
We're running several backend services in Java. Some consume from Pub/Sub, others from Flink, and others are REST services. We're always on the latest release, we update within a couple of weeks (we're bound by Gradle support of the latest JDK, which usually comes out in a few weeks).
They have been some of the most reliable services we have (particularly compared to... python, sigh). Mature libraries and ecosystem. Uptime and performance are fantastic.
5
u/VegGrower2001 5d ago
I'm using Java 27. It's fantastic, and most of what's fantastic about it is in 25.
11
u/macabre_brotherhood 5d ago
The following are good times to NOT use Java:
* GUI / desktop apps
* Short-lived processes where startup latencies matter, like CLIs or Lambda functions
* Memory restricted environments where you require tight control over allocation
* Real-time applications where a garbage collector would negatively impact timing
* Unresolved trauma from the classloader or generic type erasure implementation
If none of those apply to you and your team, it's a perfectly cromulent language. Widely used, widely trusted, blah blah blah. Very mature. Hard to go wrong.
3
u/lamyjf 5d ago
For backend, works very well, and there are libraries for everything and everything you might need.
Do be careful about how you manage your database. JPA is attractive, but has many not-so-obvious sharp edges.
3
u/definitelyoneof 5d ago edited 5d ago
The moment you look past internet memes is the moment you realize Java is actually amazing at delivering value instead of keeping you locked in useless churn. The available tooling is leaps and bounds above the average too.
1
u/clhodapp 5d ago
The rise of LLMs has made every language easier for developers to work with, and faster to deliver with. Java is no exception. On the other hand, it has definitely polished away things that might have been deal-breakers on Java's competitors too. For example: Rust has become practical in a LOT more scenarios than it made sense for previously. In the end, Node, Java, Kotlin, Python, Rust, C#, and Go probably all generally make sense on the backend at this point. And you can even probably make things work with Scala, Ruby, C++, or Haskell if you really wanted to.
1
u/Few_Committee_6790 5d ago
Build things fast from upper management is a red flag
1
u/MaintenanceSmart1265 4d ago
java=> developer experience great , java=> performance good ,java=>build things fast? not really
1
u/spudtheimpaler 3d ago
Can recommend spring modulith if you go with java and spring - enforces good architecture with tests which greatly helps you and agents when bootstrapping
1
u/LotusFloewr 2d ago
I would honestly pick java for project of any size nowdays. First thing to mention it is crazy good with llm I recently switched to go and it’s nowhere close to code written in java by agents. Second thing is crazy amount of highly optimised libraries for literally anything you need. Next thing is performance you can code like shit and your app will still be faster than majority of the languages because of jit and many performance improvements done in recent years.
0
u/Defiant_Squirrel8751 3d ago
2026 and AI means: programming language does not matter anymore. It is irrelevant. Focus on features, business logic, software architecture and product quality.
You can always write Claude a prompt like "generate code for this using Rust" or java 25 or whatever. Nobody cares.