The project
After building Travia, the GODO team came with the proposal to create a unique property management system - Property!
Because there are a lot of property management solutions in the market, our goal was to reshape the perspective and the expectations of the software in hospitality as a solution and develop a modular and role-based property management system that can easily integrate with other third-party systems and interoperate with them. The modular set-up means that the property management system needs to be flexible and fit multiple property types. Meanwhile, the role-based set-up was intended on optimizing the different parts of the system for the person that will be using it.
The challenge
The biggest challenge was to understand the variety of problems one hotel front desk is facing and shape a proper solution for them. As software consultants and executioners of the digital transformation strategy, we embraced that challenge.
Our first step was to drill down to the very core of the daily activities performed by each role involved in the property or hotel operations. Fortunately, our partners GoDo have long-standing relationships with properties of different size, setup, and needs, which helped us define various complex user stories and scenarios.
The second step was to define the architecture and the modules. We decided to go back to Travia, which was built as a monolith and already contained most of the concepts which were translated into software modules.
We decided to reuse and decouple these modules, thus giving them a separate lifeline in the form of microservices, such as:
-
Authorization
-
Property (Core)
-
Integration
-
Notifications
-
Pricing and invoicing
-
Booking
-
Inventory
-
Tasks
-
Guest Data
-
Content
Breaking up the monolith meant that we encountered new problems: communication between microservices, transactions across them, action and effects, testing, monitoring, etc. This situation encouraged us to seek a solution with Kafka, E2E test, SC Gateway, Eureka, ElasticSearch and Kibana.
The third step is related to the second challenge we have in this project - the integration and interoperability with external systems, a core requirement in the hospitality industry. This module is the one that ensures that Property can communicate and work impeccably with third-party systems, such as OTAs (online travel agencies - Booking, Expedia, etc), channel managers, and niche products (booking management systems, rate management tool, guest management tool, cleaning app, door key system, tv system, etc.). Therefore, we created a separate microservice designed to handle the communication with all the APIs, with an action/effect pattern.
The process
SPECIFICATION
-
Requirement gathering phase - meetings and workshops
-
Initial system architecture – diagrams and modules
-
Specification by example (SBE) approach
-
User stories and scenarios – Behavior Driven Development (BDD)
-
Database design
DESIGN, DEVELOPMENT & TESTING
-
Backend
-
Microservices
-
Kafka
-
Security with OAuth/JWT
-
REST API Backend in Spring Boot
-
Postgresql/MySql Database
-
Elasticsearch and Kibana
-
Integration with external APIs
-
Frontend
-
Angular NgRx
-
Material Design
-
Automated Tests
-
White-labeling
DEPLOYMENT
-
Continuous Integration / Continuous Deployment
-
TeamCity
-
Octopus Deploy
-
AWS infrastructure
-
RDS Database
-
Elasticsearch
-
EBS Application
-
S3 File Storage
-
S3 Frontend
The result
The result of this project is a clear microservice architecture that provides flexible, scalable, and robust software with different modules, enabling each client to use a palette of different services and that interoperates with almost all the external services of the industry, making it unique among other PMS providers.
Let's discuss your project.
We're all ears.
Drop us a line