Principles of Fluent API Design

on YouTube ↗19m

" summary

Defines cascading API as chainable calls that may split across statements and fluent API as a style that guarantees a single unbroken expression, then gives concrete design choices: homogeneous vs heterogeneous return types, immutable vs mutable chains, and whether terminal steps are fallible. Notes real examples: Truth is heterogeneous and immutable, Flogger is mutable and homogeneous and uses parameterized no‑ops to avoid splitting. Calls out a common bug: Stream.parallel has no parameter so it forces splitting, and recommends escape hatches and runtime checks when splitting would break correctness.

AI-written summary · about

" chapters (11)

1. 0:00Fluent API design intro
2. 1:06What defines a fluent API
3. 5:21Cascading vs fluent API
4. 6:05Why fluent APIs matter
5. 7:29Design choices for fluent APIs
6. 10:42Fluent utility pattern
7. 13:32Comparing fluent API designs
8. 14:18Benefits and trade-offs
9. 15:22Pitfalls and constraints
10. 16:46Quick tips for fluent APIs
11. 17:29Q&A

" related talks

• 46mDesigning Functional ProgramsVenkat Subramaniam · Oracle OpenWorld 2017
• 49mLet's make a contract: the art of designing a Java APIMario Fusco · Voxxed Days Ticino 2021
• 49mJava Functional Programming IdiomsVenkat Subramaniam · J-Fall 2018
• 27mModern Java API DesignJonathan Giles · Jfokus 2021
• 56mJava Functional Programming IdiomsVenkat Subramaniam · Developer Summit 2020
• 42mPure Functions and Immutable ObjectsVictor Rentea · Devnexus 2021
• 51mLet's make a contract: the art of designing a Java APIMario Fusco · Global Summit for Java Devs 2020
• 50mThe Good, the Bad and the Ugly of Java API DesignMiro Cupak · Devnexus 2020