In B2B travel, every agency, sub-agent and corporate client expects its own pricing, credit, permissions and reports. Putting the account at the centre of the data model keeps those rules manageable.
Redis is usually introduced as a cache, but its data structures solve many coordination problems. Practical patterns for rate limiting, distributed locks, request deduplication, queues and leaderboards, with their limits.
Microservices solve organisational and scaling problems, but they add distributed-systems complexity. Why a well-structured modular monolith is often the better starting point, and the signals that justify splitting services out.
Search, pricing, booking, payment, ticketing and servicing: how the parts of a modern travel booking engine fit together, where they fail, and which design decisions are hardest to reverse.
Airline content now arrives through two very different channels. A booking engine that treats them as one model, with separate adapters, avoids rebuilding every time a carrier changes course.
