An application on which regular development has been doing on for more than 2 to 3 years where a team of 5 devs would have worked. I would feel is a good starting point.

What’s your next move? Try implementing smarter retries this week, externalize your policies, and test with chaos engineering. Resilience isn’t just code—it's a mindset. Follow for more insights!

🎯 With Tenacity, you can craft tailored, adaptive retries that differentiate between permanent errors and transient hiccups. Combine this with resilience layers like circuit breakers for a truly fault-tolerant system. Success is a retry away!

🔑 The secret? Advanced retry strategies! Using exponential backoff, jitter, and exception filtering—tools that help your app recover gracefully without causing traffic spikes or masking issues. Learn how to do it right!

Building Resilient Python Applications with Tenacity: Smart Retries for a Fail-Proof Architecture In modern distributed systems, failure is inevitable. APIs experience transient outages, networks suffer from latency spikes, and third-party dependencies push unstable deployments into production eve...

✨ Failures are inevitable, but resilience is a choice. Just like a player keeps trying without frustration, building smart retries in Python keeps your system bouncing back—faster, smarter, stronger. Ready to level up?

amitavroy.substack.com/p/building-r...

I agree.

If the codebase is big, there are multiple modules, it can make sense.

But I have seen very small projects going through over engineering which is not required at all.