5 tips to make your Java apps more awesome. Non-functional Requirements Exemplified
summary
Concrete checklist with runnable demos: a two-service Java setup (API front and backend) plus an Unleash server runs under Docker Compose, built with Jakarta/MicroProfile features. Fault tolerance uses MicroProfile fault tolerance (retries, fallback, circuit breaker) and exposes counters at /metrics; the demo shows 49 calls with 8 failovers. Health probes include startup/readiness/liveness where a configured 5s artificial delay trips a 3s liveness timeout. Code and compose files are public and work end-to-end.
AI-written summary · about
chapters (8)
- 0:00Non-functional Java requirements
- 1:30Why non-functional requirements matter
- 8:54Fault tolerance in Java services
- 18:07Monitoring with probes and metrics
- 27:04Feature toggling in Java apps
- 36:10Infrastructure as code for Java
- 42:34Live demo of five tips
- 57:13Q&A
related talks
51m5 Tips to Make Your Java Apps More Awesome!
25m5 quick tips to make your Java apps more awesome
52mBulletproof Java Enterprise Applications for The Hard Production Life
01h 00mBulletproof Java Enterprise applications for the hard production life
45m12-Factor, Cloud Native Enterprise Java Applications
29mHow to develop your first cloud-native Applications with Java
55m10 strategies for developing reliable Jakarta EE & MicroProfile apps for the Cloud
51mReal World Lean Java Practices, Patterns, Hacks, and Workarounds