- Task
- Growing a short-term rental ecosystem
- Scale
- Web, iOS / Android, internal back-offices, one backend
- Role
- Technical lead: architecture, implementation, releases
- Outcome
- One server core behind several client applications
- Evidence
- Public product; figures and screenshots by agreement with the client
Problem
A multi-application rental platform spanning guest search and booking, mobile, host operations, PMS integrations, payments and owner reporting. Dozens of backend modules · hundreds of versioned migrations · extensive background and scheduled processing.
Architecture
Backend — a multi-domain Django core covering bookings, payments, PMS synchronization, background processing, WebSocket communication and APIs for several client applications; PostgreSQL / PostGIS, Redis, Celery. Web — a public client and cabinets in Vue 3: search, property pages, booking, host and organization cabinets, a standalone booking widget and custom prerendering for SEO. Mobile — a cross-platform Flutter application for iOS and Android covering guest and host flows: search and booking, maps, trips, QR login, push notifications, deep links, biometrics and Sign in with Apple (Flutter · Dart · bloc · dio · OneSignal · Yandex MapKit · Codemagic · fastlane). Internal tools — two separate React / Express systems: a host operations cabinet and an owner financial-reporting hub.
Engineering decisions
- Integrations: PMS and booking channels, payment acquiring, messengers, push, Google Sheets, maps and geocoding.
- Reliability: background queues, retries and idempotency, booking and payment reconciliation, data-quality checks, tracing and monitoring.
- One backend serves guests, hosts and owners through the web, the mobile app and internal cabinets.
- Observability and delivery: OpenTelemetry, Prometheus, Grafana, Docker, GitHub Actions.
Outcome
Led the technical side: architecture, code review, release process; worked on the backend, the Vue client, the Flutter app and two Node.js systems.