Building Bulletproof Java Enterprise Applications
Speaker: Sebastian Daschner

For more blog posts, see The Oracle Code One table of contents

Being resilient

• Don’t crash
• Prevent faiures from casading
• Don’t allow actions that are doomed to fail

Timeouts

• Avoid deadlocks
• Kill at some point so overall system and continue
• Especially http and database timeouts.
• Some libraries default to no timeouts

Retries

• Immediately retry to avoid temporary failure – but be careful that not putting more load on a failing server
• Avoid unnecessary error codes
• Decide how often and how many times to retry

Java EE Extensions

• Microservices extensions – adds timeouts and more

My take: I like that there are actual code examples. I don’t like that the text based slides are in vi (or a screenshot of vi). Such a smal font and tons of wasted whitespace.