HEXLE REST API – Central Backend Platform
At HEXLE, I developed a centralized REST API using Spring Boot to serve as the backend foundation for multiple business applications, including HEXLE Ticket, HEXLE LZE, and HEXLE Bookings.
The API acts as a single source of truth for data access, business logic, and security, ensuring consistency, scalability, and reliable integration across the entire HEXLE SaaS ecosystem.
Role & Responsibilities
Lead Architect
I was responsible for the overall software architecture, database design, and technical direction of the API. This included hands-on backend development as well as coordinating and guiding implementation decisions to meet product and stakeholder requirements.
Core Technologies
- Java
- Spring Boot
- REST APIs
- Relational Databases (MySQL with Hibernate)
- Thymeleaf Frontend
- Maizzle (Email templating)
Integration & Architecture
- Centralized REST API serving multiple interconnected business applications (Monolithic architecture)
- Shared authentication and authorization mechanisms across services (JWT, OAuth2, PCKE)
- Database-driven architecture ensuring consistent data models
- Backend integration for Maizzle, enabling styled and templated transactional emails
- Designed for modularity and long-term scalability within the HEXLE ecosystem (Potential future migration to microservices)
Key Contributions & Impact
- Designed and implemented the core REST API used across all major HEXLE applications
- Created the software architecture and database model from the ground up
- Ensured secure, consistent data access for multiple SaaS products
- Integrated email delivery infrastructure using Maizzle for branded, styled client communication
- Oversaw the full development lifecycle, from concept to productive use
- Ensured seamless integration with existing and evolving HEXLE systems
Learnings & Takeaways
- Deep experience designing scalable backend architectures for multi-application ecosystems
- Strong understanding of API-first development and shared service design
- Practical knowledge of aligning architecture decisions with business and product needs
- Experience designing backend structures with responsibility for long-term maintainability