Tech Lead
ZooverNov 2020 - Apr 2023
Tech lead at Zoover: built one multitenant platform for two travel brands, about 9 microservices from booking to payment, and cut CI feedback from 30 minutes to 2.
Technologies Used
- Google Cloud Platform
- App Engine
- Cloud Run
- Python
- Node.js
- PostgreSQL
- Hasura
- Kubernetes
- Grafana
- Terraform
- Adyen
I led backend engineering for two Dutch travel sites, Zoover and Vakanties.nl. The big job was running both brands on one shared backend.
The companies
Zoover is a Dutch travel site where people share holiday reviews, photos and videos, and book accommodation and trips.
Vakanties.nl is a travel agency. You book a package, then swap parts of it: a different flight or hotel, a rental car instead of a transfer. It sells trips from several large tour operators and is a member of ANVR and SGR.
What I did
One backend, two brands
Vakanties.nl bought Zoover, and each brand came with its own reservation and payment systems. One had to go. The choice was to phase out Zoover's reservation system and run both brands on the Vakanties.nl reservation engine, turned into a multitenant, service-oriented platform with shared services and room for each brand's own rules. Most of my backend work was on that move.
I designed and maintained about 9 microservices end to end, covering the whole booking flow from the booking session to the final payment. The platform handled thousands of bookings a month.
That meant agreeing on one stack, one set of patterns and one place for the architecture docs, so engineers could work on either brand.
CI/CD from 30 minutes to 2
Every change waited about 30 minutes for pipeline feedback, and that blocked delivery across teams. I moved us to monorepos with isolated pipelines, so each service only built and tested what changed. Feedback dropped to 2 minutes.
Data access with Hasura
We had a lot of APIs to work with, so we put Hasura in front of PostgreSQL as the middleware for all of them. It was one of the best decisions we made. It gave us GraphQL APIs and real-time queries without hand-writing resolvers, and its declarative migrations kept schema changes versioned and repeatable.
Payments
I led the integration with Adyen for payment processing, including multiple currencies and payment methods, and the monitoring and reconciliation around it. I have built Adyen payments at almost every company I worked for in the Netherlands. A month after leaving Zoover, I joined Adyen itself.
Keeping it running
This was a customer-facing app, so speed and responsiveness were part of the user experience. The services ran on Kubernetes with a caching layer, auto-scaling and load balancing, and I worked closely with the frontend team on it.
The reservation data itself came from an accommodation aggregator, the same source that big tour operators such as TUI draw from. APIs were versioned to stay backward compatible.
We made sure the platform was GDPR compliant, and tracked bugs and errors in production.
Leading the team
I was tech lead for 6 to 7 engineers and mentored 4 of them on system design and technical direction.
- Set the technical roadmap with product and business, trading delivery speed against maintainability
- Ran knowledge-sharing sessions
- Set coding standards and a code review habit across the backend services
- Reworked team workflows and onboarding for new engineers
Stack
- Google Cloud: App Engine, Cloud Run, Cloud Identity, Secret Manager, Cloud Scheduler
- Services: Python and Node.js, REST and GraphQL APIs
- Data: PostgreSQL with Hasura
- Operations: Kubernetes, Grafana dashboards and alerts, Terraform, CI/CD pipelines
What I took from it
This was my move from senior engineer to lead. The hard part was not the architecture. It was keeping my hands in the code while giving the team room to own it.
Multitenancy also taught me that sharing code between brands is cheap. Sharing decisions between two business teams is where the time goes.