Spring Boot Done Right: Lessons from a 400-Module Codebase
1–10 of 100 posts
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#2Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#3Does this app take 5 minutes to start? That's so much dynamic Spring magic. Also, how do you keep track of control flow when anything at anytime could have been overridden by something else? It seems like tracing and debugging this thing would be like exploring someone else's codebase every time.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#4Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
it saves a lot of reinventing the wheel
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#5I recently inherited java code base.
Just rewrote it in Go. Now we are using a server which consumes 30% of ram what the existing one used to and the latency and throughput have all improved.
Don't use these stupid java backend like sprinboot.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#6Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
it saves a lot of reinventing the wheel
And at the same time, gives you a dozen of footguns. This is just a list for the gotchas in the "@Transactional" annotation - https://dev.to/closeup1202/8-spring-transactional-pitfalls-t...
Now read up on all the dozen of annotations. But yeah, we did not want to "re-invent the wheel".
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#7Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
Yes but enterprise software is some of the worst software you will encounter.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#8Ops person here who has supported Java/SpringBoot applications. I think most of dislike of Java apps comes not from language or framework BUT from fact that most Java using workspaces are filled with mediocracy. They tend to be businesses with products that have extreme moats and thus quality of software barely matters. I imagine most people who would even read this medium article are dreaming of better than that.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#9Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
Huh, Enterprise usage of Blackberry was very very high and then it was not. And at one point SOA, SOAP/WSDL/XML usage was very very high and now I am told in my very enterprise job I'd be fired if I dared bring those names up.
Usage being high doesn't say anything about quality or suitability of a product specially in enterprise settings.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#10I recently inherited java code base. Just rewrote it in Go. Now we are using a server which consumes 30% of ram what the existing one used to and the latency and throughput have all improved. Don't use these stupid java backend like sprinboot.
I wouldn’t reduce it to don't use Java/Spring Boot. Rewrites often (not always) look great because they remove years of accumulated complexity, not because the original stack was inherently bad.
Just rewrite it in X doesn't "just work" for complex systems. It ignores risk, and the fact that design usually matters more than language.