I've been building booking software for a while, and every project starts with the same conversation.
"They want online booking." Fine. "They have five staff, three rooms, and two locations." Still fine. "And the platform should let other shops sign up and run their own booking page under their own brand." That's the moment where the requirements stop being a calendar widget and start being a multi-tenant product.
I ended up building that product. It's called Skeduvo, and this post is about the three architectural decisions that shaped it: row-level multi-tenancy, generated time slots, and treating the customer booking page as an installable web app instead of a native app.
The stack
Layer Choice
Backend Java 21, Spring Boot 3.5, Spring Security, Spring Data JPA / Hibernate
Database MySQL 8 ( utf8mb4 )
Frontend Vue 3.5, Element Plus, Vite 6, vue-router, vue-i18n
PWA vite-plugin-pwa (Workbox)
Deployment Docker Compose, Nginx, MySQL 8.4
Nothing exotic. That was intentional.…