AI Writes the Spring Boot API, the Contract Keeps It Honest

You’ll learn: let AI build your Spring Boot APIs while the contract catches every drift from the design.

Register NowPresented byHarshvardhan Parmar

• ✓Keep a reviewed API specification as the single source of truth while an AI agent writes the code
• ✓Spot drift that compiles and passes generated tests: wrong fields, enum values, status codes, validation rules and response behaviour
• ✓Continuously validate the running Spring Boot service against its contract
• ✓Feed contract failures back to the coding agent in an iterative repair loop until the API behaves as designed

AI coding agents can now generate Spring Boot APIs incredibly quickly. But speed creates a new problem: how do we know the generated implementation actually matches the API we designed?

A service can compile, start successfully, and even pass generated tests while still drifting from its contract through incorrect fields, enum values, status codes, validation rules, or response behaviour.

In this session, we’ll explore a spec-driven development workflow where the API contract remains the source of truth. We’ll start with a reviewed API specification, use it to guide an AI agent while building the Spring Boot implementation, and continuously validate the running service against the expected contract.

We’ll also look at how contract failures can be fed back into the coding agent to create an iterative repair loop until the implementation behaves as expected.

Harshvardhan Parmar

Maintainer @Microcks

Maintainer of Microcks, a CNCF Sandbox project, Google Summer of Code 2024 alumnus and LFX mentee who leads Microcks-CLI.

Harshvardhan is an enthusiastic open-source contributor, a passionate advocate for cloud-native technologies and a maintainer of Microcks, an open-source CNCF Sandbox project.