Let's make a contract: the art of designing a Java API
summary
Design rules for Java APIs that actually help users: treat the API as a contract, document ranges and defaults and surface preconditions so callers don't have to guess, prefer return interfaces not concrete classes so implementations can evolve, and preserve compatibility by hiding mutable state and using a single entry point factory methods instead of forcing users to construct internals. Examples reference standard Java types, stream-like producers, and concrete mistakes like returning subclasses or leaking internal collections.
AI-written summary · about
chapters (7)
- 0:00Introducere în API-uri Java
- 5:30Principii de bază în proiectare
- 15:42Documentație și claritate
- 23:20Flexibilitate și viitor
- 33:14Siguranță și protecție
- 43:32Evoluție și compatibilitate
- 51:10Concluzii și Q&A
related talks
49mLet's make a contract: the art of designing a Java API
27mModern Java API Design
34mDesigning a Compatible API — Genius Without Villainy
44mMastering Resilient Java API Design: From Principles to Practice
52m10 Reasons Why we Love Some APIs and Why we Hate Some Others
01h 08mJava APIs - the Missing Manual
15mHow to Design Effective APIs | Actionable Guide
01h 18mAPI design: Lessons Learned