Reactive Spring Boot API Integrations

Our high-performance sports data platform already streams vast amounts of live statistics; what I need now is a Spring Boot specialist who can turn that firehose into clean, non-blocking APIs. The most critical focus is the integration layer itself—every endpoint you wire must embrace WebFlux, WebClient, and Mono/Flux so we stay fully reactive from request to database and back.

You’ll be pairing Gradle builds with PostgreSQL, pushing updates through asynchronous pipelines, and designing endpoints that scale under game-day traffic without a hiccup. Concretely, you will integrate data flowing from:

• Internal APIs
• External APIs
• Third-party services

Because these three sources differ in latency and payload structure, thoughtful back-pressure handling, retries, and error propagation are essential.

Deliverables
• A modular, Gradle-managed codebase exposing the new reactive API layer
• Integration and load tests proving stability at high concurrency
• Concise README outlining configuration, run commands, and performance benchmarks

Acceptance criteria
• All API calls remain non-blocking end-to-end (verified via tests)
• Response times hold steady under simulated peak load
• No blocking JDBC calls—PostgreSQL access must use reactive drivers

When you reply, point me to past work that highlights similar reactive or sports-data projects so I can gauge fit quickly. If your portfolio shows you’ve wrestled with WebFlux under real pressure, we’ll move fast.