I built a Travel Data Platform API in .NET - search, analytics, and recommendations with Redis caching

Most travel APIs I have seen treat search, analytics, and recommendations as completely separate systems. Different teams, different databases, different codebases. This project explores what it looks like to build all three on a single clean data model, with caching built in from the start rather than bolted on later. What it does The platform has four areas. Ingestion accepts bulk flight and user data via POST endpoints. In a real system this would connect to partner feeds or scrapers. Here it seeds 240 flights across 12 routes with realistic pricing. Search lets you filter flights by origin, destination, airline, price, and departure date. All results are paginated. Every unique combination of filters gets its own Redis cache key, so a repeated search returns in under 100ms instead of hitting the database. Analytics exposes three aggregated views - popular routes ranked by volume, monthly price trends for any route, and peak travel periods by month. These are the endpoints a commerc