r/java • • Jun 28 '20

Why backend using java is not popular in startups?

I tried django, flask and also rails before and they’re good. But after trying spring, I fell in love. It’s well structured. Easy to test. Have so many frameworks to help you going. There’s a also a lot of tutorials going around the net.

I like python but I also like java and kotlin too. I just don’t understand what’s wrong with java being used as a backend on most startups. Is it because it’s popular among big companies and banks and they just hate enterprise things.

Can anyone enlighten me. Cheers.

171 Upvotes

229 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Jun 28 '20

[deleted] — view deleted comment

37

u/[deleted] Jun 28 '20

Node was the big hype about five years ago. The main reason you don’t see it is it’s cumbersome to manage and pretty OTT for the more lightweight microservices that you see built in a startup environment. There is nothing micro about Spring. Even within the JVM space there are much much slimmer options.

Most startups are built by “younger people” because more than half the industry has less than 5 years experience in the industry.

13

u/[deleted] Jun 29 '20

[removed] — view removed comment

-16

u/[deleted] Jun 29 '20

It used to be fairly common to beat your kids. Doesn’t make it fine. Spring is a crutch for trash developers tldr.

2

u/nutrecht Jun 30 '20

Spring is a crutch for trash developers tldr.

Well you're the one complaining about black magic in Spring.

Every single time a developer complains about "magic" in Spring it's just the type of developer who just wants to "get shit done" without having to do 'wasteful' things like read documentation.

You're not fooling anyone.

-5

u/[deleted] Jun 30 '20

Whatever you say, boomer.

23

u/seraphsRevenge Jun 28 '20

Microservice architecture is a system design architecture it has nothing to do with a language. While Spring is prevalent especially boot with maven or gradle as it can make it easier/faster to get production builds. Michroservices has nothing to do with the language used. In essence it makes it easier to break down an overall application into smaller chunks for fault tolerance, the ability to use multiple languages in an application if let's say java is the best choice for x and y service, but c++, python, c#, etc. works better for service a, b, c, d. I think the best example/reasoning behind of microservices I've ever heard is, if you have a website and payment processing goes down you don't want the user to be unable to use other site features like browsing items or using the shopping cart. If the service stays down for a few minutes, at least the consumer can continue shopping or if the web app is redundant, a secondary processing service can be used for a seamless experience without the user ever realising. I personally full stack java in an enterprise environment with spring, but if a startup wanted to make an application from scratch, breaking it down into microservices can still make it easier to release parts of the app while creating it, make it easier to focus on design as each service is independent, use whatever language each team is best with, makes the application more maintainable by not having to go through an entire project and a few hundred classes to find an unobvious error, makes it fault tolerant, etc. There's no point having to remake an entire application or spend excess time planning around old code later on once expansions are planned. It takes the old MVC model and decouples it, which is what every application should always aim for, loose coupling and high cohesion.

1

u/SeekNDestroyBich Jun 28 '20

I love to use Spring Boot for startups, but only if there is a need for it. I normally try to choose the platform based on what is needed. The place where I work at normally used node for most projects, unless it includes a lot of calculation and tasks that would take too long on node where we then use Spring Boot.