<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Openapi on Sang Sinh NGUYEN</title><link>https://www.sinhnguyen.dev/tags/openapi/</link><description>Recent content in Openapi on Sang Sinh NGUYEN</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Nov 2026 00:00:01 +0000</lastBuildDate><atom:link href="https://www.sinhnguyen.dev/tags/openapi/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 2. Where Does processEvent Come From?</title><link>https://www.sinhnguyen.dev/blog/contract-first-part-2-inside-the-generator/</link><pubDate>Tue, 10 Nov 2026 00:00:01 +0000</pubDate><guid>https://www.sinhnguyen.dev/blog/contract-first-part-2-inside-the-generator/</guid><description>Opening the code generator behind platform.yaml: how an AsyncAPI schema becomes Java models and the delegate interface we implement, plus a playground you can type into.</description></item><item><title>Part 1. Contract First: Letting the Spec Write the Code</title><link>https://www.sinhnguyen.dev/blog/contract-first-part-1-spec-writes-the-code/</link><pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.sinhnguyen.dev/blog/contract-first-part-1-spec-writes-the-code/</guid><description>How we moved Lambda ports onto AsyncAPI and OpenAPI contracts, declared them in one platform.yaml, and let a generator write the event models, SQS consumers and HTTP clients we used to write by hand.</description></item></channel></rss>