Spring Framework 7.0 has officially introduced Built-in Concurrency Limiting and Retry Support using the new resilience annotations in the Nov 2025 release. 𝐖𝐡𝐚𝐭’𝐬 𝐍𝐞𝐰 𝐚𝐧𝐝 𝐖𝐡𝐚𝐭’𝐬 𝐒𝐭𝐢𝐥𝐥 𝐢𝐧 𝐏𝐫𝐨𝐠𝐫𝐞𝐬𝐬 🤷♂️ New features added to the spring core: - @Retryable for declarative retries - RetryTemplate for programmatic retry control - @ConcurrencyLimit for throttling concurrent access Means, no more need for the external spring-retry dependency. And, that's really awesome 👍 Sam Brannen mentioned in his blog that the current core retry support is still minimal and in active development. 🔴 It does not yet include everything that spring-retry used to provide — for example, the convenient @Recover mechanism. ℹ️ The feature request for a @Recover equivalent is still open on GitHub: Open Issue 👉 https://lnkd.in/e_CD_Q-s In other words, Spring 7 gives you the foundation for retries and resilience, but some higher-level features are still on the roadmap. For now, programmatic handling with RetryTemplate is the way to implement fallback behavior. 📖 Official blog: https://lnkd.in/ezgReFTH I hope you find it helpful! #SpringFramework #Java #JavaDevelopment #SoftwareEngineering #Microservices #SpringBoot #SpringCore #Resilience #RetryMechanism #Concurrency #SoftwareDevelopment #TechUpdate #EnterpriseJava #SpringCommunity #Programming #DevCommunity
Lemrabott Toulba’s Post
More Relevant Posts
-
Say goodbye to NullPointerException? Spring Boot 4 and JSpecify are changing the game. With the move to Spring Boot 4 (and Spring Framework 7), we're seeing a massive, deliberate shift towards compile-time null-safety. This isn't just about using Optional anymore. Spring is embracing JSpecify annotations (@NullMarked and @Nullable). This allows the framework and just as importantly, our own code to explicitly declare nullability contracts. What this means for developers: 1. Catching NPEs at Compile-Time: By integrating tools like NullAway, we can find and fix potential NullPointerExceptionsduring the build, not in production at 2 AM. 2. Cleaner, More Expressive APIs: Your code's public API now clearly states what's allowed to be null and what isn't. No more guessing. 3. IDE Superpowers: IDEs like IntelliJ IDEA can provide instant, accurate feedback, guiding us to write safer, more robust code from the first line. This is a huge step forward for production-grade Java applications. The "billion-dollar mistake" is finally getting a proper fix in the Spring ecosystem. What are your thoughts on this new approach to null-safety? #SpringBoot #Java #SpringFramework #NullSafety #JSpecify #Developer
To view or add a comment, sign in
-
Why Every Spring Boot Developer Should Understand @Transactional Deeply Most of us use @Transactional daily — but few truly know what happens behind the scenes. Here’s the real story 1️⃣ When you mark a method with @Transactional, Spring creates a proxy around your bean. 2️⃣ This proxy manages the database connection and transaction context. 3️⃣ If the method finishes successfully → ✅ Transaction commits. 4️⃣ If a runtime exception occurs → 🔁 Spring rolls back automatically. ⚡ Pro Tips: Rollback doesn’t occur for checked exceptions unless explicitly configured. Self-invocation (calling another @Transactional method in the same class) → ❌ no new transaction triggered! Understanding this behaviour helps you avoid hidden bugs and build reliable, production-grade systems. #SpringBoot #Java #Microservices #BackendDevelopment #Transactional #SystemDesign #CodeQuality #Programming #Rajkumar
To view or add a comment, sign in
-
🚀 Debugging @Async in Spring Boot Was wondering why my async method wasn’t actually running in parallel… After some digging, I realized the issue: 👉 I was calling it from the same class, so Spring’s proxy never intercepted the method call. 💡 Lesson learned: @Async (just like @Transactional) only works when the method is invoked through the Spring proxy, not directly within the same bean. ✅ Moving the method to a separate service (or injecting the bean into itself via proxy) instantly fixed it. It’s a good reminder — many Spring features are just smart proxies under the hood. Understanding that saves hours of debugging! Have you ever hit similar proxy or async issues in Spring Boot? #TodayILearned #SpringBoot #Java #Microservices #BackendDevelopment #AsyncProgramming #SpringFramework #LearningInPublic #JavaDevelopers #TechTips #CodeBetter
To view or add a comment, sign in
-
Are we finally fixing the billion dollar mistake? 👀 Spring Boot 4's null safety improvements might be the most underrated feature in the upcoming release. NonNull and Nullable annotations are now first-class citizens across the entire framework. Spring is migrating its entire codebase to use these consistently. No more guessing if that service method might return null. Your IDE catches NPEs at compile time, not runtime. Is this the correction Tony Hoare wished for? Not entirely, but it's a significant step toward safer Java code. The best part? You don't need to adopt it all at once. You can migrate incrementally, making your codebase safer and giving you more confidence with each step. #SpringBoot4 #Java #SpringFramework https://lnkd.in/g_xe72Jr
To view or add a comment, sign in
-
"𝙎𝙥𝙧𝙞𝙣𝙜 𝘽𝙤𝙤𝙩 𝙙𝙤𝙚𝙨𝙣’𝙩 𝙘𝙤𝙣𝙛𝙪𝙨𝙚 𝙮𝙤𝙪. 𝙄𝙩 𝙥𝙧𝙚𝙥𝙖𝙧𝙚𝙨 𝙮𝙤𝙪 𝙛𝙤𝙧 𝙧𝙚𝙖𝙡-𝙬𝙤𝙧𝙡𝙙 𝙨𝙮𝙨𝙩𝙚𝙢𝙨." When you finally understand Spring Boot… and then Spring Boot hits you with 27 new annotations you’ve never seen before 🤯 As Java developers, we all start with the basics: ✔️ Controller ✔️ Service ✔️ Repository …and think, “𝙊𝙠𝙖𝙮, 𝙣𝙖𝙖𝙣 𝙢𝙖𝙨𝙩𝙚𝙧 𝙖𝙖𝙮𝙞𝙩𝙚𝙣.”😎 But the deeper you go, Spring Boot teaches you something important: 👉 Enterprise development isn't about writing code. It’s about writing scalable, maintainable, testable, production-ready systems. And that’s where the so-called “magic” comes in — dependency injection, auto-configuration, profiles, AOP, caching, validation, event listeners, starters… the list never ends. But here’s the real truth: Spring Boot isn’t trying to confuse you. It’s teaching you how real-world software works #Java #SpringBoot #SpringFramework #BackendDevelopment #SoftwareEngineering #JavaDeveloper #CodingJourney #ProgrammingHumor #TechCommunity
To view or add a comment, sign in
-
-
Today I learned something interesting about Spring Boot’s @Async annotation. I was debugging why an async method wasn’t actually running in parallel — and eventually realized it was because I was calling it from within the same class. Since the call never went through the Spring proxy, the @Async behavior didn’t trigger. Lesson: @Async only works when the method is invoked through a Spring-managed proxy — not via direct internal calls within the same bean. Moving the method to a separate service (or injecting the bean itself via a proxy) fixed it instantly. A small reminder that many “magic” framework features are really just smart proxies under the hood — and understanding how they work can save hours of debugging. Have you ever run into similar proxy or async surprises in Spring Boot? #TodayILearned #SpringBoot #Java #Microservices #BackendDevelopment #LearningInPublic
To view or add a comment, sign in
-
🚀 Spring Boot 4: Real Null-Safety at Last! For years in Java we’ve played the guessing game around null. When you see a method like: User findUserByEmail(String email) Can it return null? Maybe. Maybe not. You hope it won’t… and sometimes — 💥 boom — a NullPointerException in production. With Spring Boot 4, that uncertainty is finally over. Thanks to the @NullMarked support (via JSpecify & NullAway) the nullability of your APIs becomes explicit. Here’s what it means in practice: Add @NullMarked at the package level → by default, types are non-null unless annotated otherwise. The IDE (IntelliJ, Eclipse, VS Code) immediately shows where nulls are risky. The compiler and build tools (via NullAway) help you fix issues before runtime. Every parameter, return type and field clearly tells you whether it can be null or cannot. Your code becomes more predictable, more readable, and above all — safer. 💡 Daily benefits: ✅ Fewer bugs and production surprises ✅ Clearer method and API contracts ✅ Self-documenting code for teammates and reviewers ✅ Easier code reviews and maintainability ✅ Better interoperability (especially with Kotlin, which understands nullability) But null-safety isn’t the only upgrade in Spring Boot 4.0. Among other improvements: Baseline requirement of Java 17+ — unlocking records, sealed classes, pattern-matching, better performance. Enhanced native image and ahead-of-time (AOT) compilation support, making microservices start faster and use fewer resources. Improved API versioning support, so evolving REST-APIs become easier to maintain side-by-side. In short: Spring Boot 4 doesn’t just add features — it upgrades the developer experience and makes your entire codebase more trustworthy. 💪 If you’re tired of endless Optionals, manual null checks, and unpredictable NPEs — it’s time to take the leap. #SpringBoot #Java #CleanCode #NullSafety #DeveloperExperience #JSpecify #NullAway
To view or add a comment, sign in
-
This Is Why Spring Boot Wins… Every. Single. Time. 🚀 As developers, we’ve all seen how the ecosystem keeps evolving—fewer lines of code, more productivity, better scalability, and cleaner architecture. This meme perfectly captures the journey from traditional Java to Spring and finally Spring Boot. What once took thousands of lines can now be achieved with simple annotations and opinionated configurations. Every upgrade in the Java ecosystem isn’t just about writing less code—it’s about building smarter, faster, and more efficient applications. 💡 That’s the beauty of modern frameworks: they let us focus on solving real problems instead of managing boilerplate. #Java #Spring #SpringBoot #SoftwareEngineering #DeveloperLife #CodingHumor #TechCommunity #Programming #FullStackDeveloper #Productivity
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development