Earlier quoted context omitted.
Funny how that works - I started with Spring both before and after Boot as well as some Scala. I wouldn’t trade Java / Spring for the world. It forces a coherence, perhaps not perfectly, but it provides guidelines to follow. I’ve been stuck in Node / TypeScript / Microservice hell for most of the last 15 years and I couldn’t hate it more. The open-source ecosystem is extremely lacking, even now, on something like a g…
I’ve Been stuck with Spring for many years too and I think it’s just awful choice for micro services that need to scale, simply due to startup time. Not to defend Nodejs ecosystem - your points are 100% valid. With that in mind, I think Go is much better option.
Spring Boot Done Right: Lessons from a 400-Module Codebase
51–60 of 100 posts
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#52Earlier quoted context omitted.
it doesn't mean that usage of something being very high is a clever idea. lots of people take meth - so are you gonna take meth too. ```@EnableConfigurationProperties(CasConfigurationProperties.class) @EnableScheduling @ConditionalOnFeatureEnabled(feature = CasFeatureModule.FeatureCatalog.SimpleMFA) @AutoConfiguration @Import({ CasSimpleMultifactorAuthenticationComponentSerializationConfiguration.class, CasSimpleMult…
That's a ridiculously extreme example, IME. Having been working with Java for 25+ years, I've never seen anything like that in code written by a shop I worked at, FWIW. And as a corollary I'm about 100% certain that you could find some equivalent extreme case to use as an example to dunk on any language/platform. this is what we mean by "JavaCulture" - java | JVM really wonderful things but the culture is what sets t…
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#53Ops 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.
Alternatively, I think of Java and Spring Boots as being incredibly valuable by letting companies that don't really have software as a core competency to make reasonably performant and structured applications. Mediocrity will never not exist, and you unlock a lot of value by optimising for it.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#54Earlier quoted context omitted.
Funny how that works - I started with Spring both before and after Boot as well as some Scala. I wouldn’t trade Java / Spring for the world. It forces a coherence, perhaps not perfectly, but it provides guidelines to follow. I’ve been stuck in Node / TypeScript / Microservice hell for most of the last 15 years and I couldn’t hate it more. The open-source ecosystem is extremely lacking, even now, on something like a g…
I hear this a lot from a lot of my coworkers who like Java Spring - they trust Spring to do things right, more than themselves. On the other hand, I hate Java Spring because I feel like I don't trust it - it doesn't let me look into and understand the internals easily, making me feel like I'm afloat on a pile of abstracts I'm not allowed to look down into. Looking at some other projects enterprise js/ts codebases tho…
what does this mean? you can single step into framework code
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#55Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
it doesn't mean that usage of something being very high is a clever idea. lots of people take meth - so are you gonna take meth too. ```@EnableConfigurationProperties(CasConfigurationProperties.class) @EnableScheduling @ConditionalOnFeatureEnabled(feature = CasFeatureModule.FeatureCatalog.SimpleMFA) @AutoConfiguration @Import({ CasSimpleMultifactorAuthenticationComponentSerializationConfiguration.class, CasSimpleMult…
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#56Does 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.
Oh man, just wait till you start sprinkling some AOP in there. My debugger is damn near useless sometimes as I try to follow bizarre paths between parts of my code.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#57Hacker news likes to dunk on Spring Boot, but its usage in enterprises is very very high.
I'm not that deep into Java, but I was under the impression that things like Quarkus were starting to replace Spring in enterprise use...
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#58Does 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.
Who cares about startup times if apps is started only when new version is deployed? And 5 minutes is a bit long, maybe someone is doing some database operations during start?
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#59Does 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.
> It seems like tracing and debugging this thing would be like exploring someone else's codebase every time. Oh man, just wait till you start sprinkling some AOP in there. My debugger is damn near useless sometimes as I try to follow bizarre paths between parts of my code.
Re: Spring Boot Done Right: Lessons from a 400-Module Codebase
#60Earlier quoted context omitted.
I’ve Been stuck with Spring for many years too and I think it’s just awful choice for micro services that need to scale, simply due to startup time. Not to defend Nodejs ecosystem - your points are 100% valid. With that in mind, I think Go is much better option.
Spring may be a bad choice for microservices (context required, because it is not true in general), but it is strange to compare it (DI framework/mvc/orm abstraction etc) with Go (programming language). Java exists in many flavors, you do not have to use Spring to build a performant microservice.