Opening Keynote
summary
Argues that the concrete path to reliable APIs is starting with a domain model (example: e‑commerce orders, items, addresses), turning that into reusable schemas (borrowing from schema.org), generating Java POJOs and OpenAPI or GraphQL specs, and using prescriptive patterns and annotations to auto-produce consistent REST endpoints and UIs. Adds event contracts with AsyncAPI (Avro/Kafka support) and an anything modeling language a.ml to capture workflows so teams can scaffold implementations, docs and SDKs.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:36Why Is the Business So Interested in It
- 7:27Coherence Economy
- 9:58Domain Model of E-Commerce
- 16:16Api Specification
- 25:12General Architecture
- 28:51Async Api Specification
- 31:21Schema Format
- 32:14Takeaways
- 35:21And if You Ping Me Later I Guess My Slide Is Off but if You if You Contact Me I'M Happy To Connect You or Just Go to a Dot Ml and You Will Actually Find Links from There and that's a Really Critical Point like We'Re Not in the Business of Replacing Everything We'Re in the Business of Making Everything Interoperable and Making Sure that New Things Are Even More Consistent than We Were than They Were before any Other Questions There in What You Showed How Do You Handle One-to-Many and Many-to-Many Relationships between these Entities So since I Have Many Layers
- 38:02But There Are Also Business Rules Governing How the Data Gets In and Gets Out Is the Metadata Definition Which Was Used in Rimmel Capable of Delivering those Business Rules Out to the Client so They Can Expect What to How the Aps Would Behave some of the Business Rules Yes and some of the Business Rules no and I Think the the Really Interesting Thing Is about Business Rules Is You Don't Actually Want To Expose all of Them on the Front Side of the Api There Are Many Things That You Want to Abstract Out for Two Reasons One Is It's Kind of None of the Clients Business and How You Actually Do that So for Example When I Create the the When I Create a Payment What Are the Business Rules about Verifying
- 38:21And I Think the the Really Interesting Thing Is about Business Rules Is You Don't Actually Want To Expose all of Them on the Front Side of the Api There Are Many Things That You Want to Abstract Out for Two Reasons One Is It's Kind of None of the Clients Business and How You Actually Do that So for Example When I Create the the When I Create a Payment What Are the Business Rules about Verifying and So On Obviously Should Not Be in There
- 38:44The Other Reason Is because if You Do Expose all of the Business Rules behind the Scenes You Will End Up Coupling the Client to Them and that's Actually Pretty Hard Having Said that There Are Business Rules That You Actually Want To Explain One of the Business Rules Is Obviously What Are the Business Flows So What Happens from Here to Here and So on You Do Actually End Up Reflecting that in that Restful Model and As Much as Possible those Should Be Conventional Right so There's no There's no Big Surprises in There for the Parts of Business Rules That Have To Do for Example with Validation Right so the Amount of this Order Must Be above this and So on You Can Actually Capture those In in Your Schema Rules
related talks
27mBuilding Great Web APIs
06mKeynote: APIs, the Universe, and Everything
49mBuilding Software Better: API Lifecycle Management for Developers
44mCrafting Great APIs with Domain-Driven Design
19mUnlock API and Data – The Power of Data Model and Governance
27mUnlocking API Success: Bridging Business & Engineering
28mThe New API Stack
26mRevolutionizing Business with API-First Strategy: Key Insights