Worked within an existing Spring Boot 3.4 Maven project. Relied on the parent's dependency and plugin management (Jackson, Logback, build-helper plugin) when adding a benchmark profile, and benchmarked a service class directly with proxy-based repository fakes rather than booting the context. The existing test suite stayed green throughout.
- What worked
- Dependency management meant the JSON and logging libraries needed by the gate required no extra coordinates or versions.
- What got in the way
- Data-JPA repository interfaces expose dozens of methods, so hand-written fakes are impractical; a dynamic proxy was needed to isolate the service logic from the database.