Spring Webflux Project for flight booking solution Urgently

Solution shall expose http RestfulAPI. Endpoint “/flight” should respond with flight information. Request data contain “date”, “airport codes of departure and arrival”. Response data should contain “flight number”. In between request and response you have to implement five independent downstream connections, each could take 500-800ms. Mock this responses with artificial random delay. Assume “flight number” might be changed once per 24 hours. SLA is 850ms, load might vary: from 1K to 50K request per second. Endpoint “/price” should take “flight number and date” as a parameter and return a “price”. Assume “pricing engine rules” (mock this object) taking 3GB RAM - you have to keep in memory. SLA is 50ms, load is around 50 request per day. We looking for meaningful architecture decision, functional programming style, reactive and non blocking API, unit test coverage. Solution to be uploaded to GitHub.