dknj

7 ms·

1.
Building a Plugin Architecture in Spring Boot Without Inventing a Framework(medium.com)
1 points by dknj 6mo ago|0 comments
2.
by dknj 6mo ago
Or just vibe-code whatever you want/need with Claude and enjoy life. That's the new world we live in :-)
3.
Testing a 400-Module Spring Boot Application: Patterns That Scale(medium.com)
1 points by dknj 6mo ago|0 comments
4.
by dknj 6mo ago
Good question - quite a few actually. @ConditionalOnMissingBean on every public @Bean method, proxyBeanMethods = false on every @Configuration class, the thin wrapper pattern (auto-config classes must have empty bodies) - those are all stru
5.
by dknj 6mo ago
That's fair - it does look odd in isolation. But the alternative is mixing "should this load?" conditional logic with "what should load?" bean definitions in the same class. When you're debugging why a feature
6.
by dknj 6mo ago
That's really the whole thesis. None of the patterns in the article are clever or novel - @ConditionalOnMissingBean has been in the Spring Boot docs since day one. What's hard is getting a team to apply it on every single bean, in
7.
by dknj 6mo ago
Exactly!
8.
CAS Internals – 825 pages on how a 400-module Spring Boot app works(leanpub.com)
1 points by dknj 6mo ago|1 comments
9.
by dknj 6mo ago
I've been a committer on Apereo CAS ( https://github.com/apereo/cas ) since the 3.0 days. It's an open-source SSO/identity platform - 400+ modules, Spring Boot 3.x, Java 21+. Deployed at thousands of unive
10.
Spring Boot Done Right: Lessons from a 400-Module Codebase(medium.com)
75 points by dknj 6mo ago|95 comments