Skip to content
English
Go to likemagic.tech
  • There are no suggestions because the search field is empty.

Platform Documentation

LIKE MAGIC’s platform documentation provides a comprehensive overview of our cloud-native architecture, integration framework, and design principles that power seamless digital guest and staff experiences.

Introduction

LIKE MAGIC is a user-centric, cloud-native hospitality platform built to simplify and enhance the digital guest and staff experience. Designed with open integration principles, the platform enables properties to deliver seamless self-service while maintaining operational control and data ownership.

This document outlines the architectural approach, integration design and process flow that power the LIKE MAGIC ecosystem.

 

Table of contents:

  1. Platform Technology & Principles

  2. Big Picture – Platform Overview

  3. Platform Infrastructure

  4. Microservices & Connectors

  5. Integration Principles

  6. Semantic Domains

  7. Processes - Self-Service Guest Journey

  8. Conclusion

1. Platform Technology & Principles

LIKE MAGIC is engineered for resilience, scalability, and openness. Key architectural principles include:

  • Event-driven integration with event sourcing and CQRS

  • Cloud-native, polyglot microservices architecture

  • 12-Factor App methodology: portable, scalable, and DevOps-ready

  • Use of managed services over building everything in-house

  • Built with Spring Boot WebFlux (backend) and React (frontend)

Key components:

  • Databases & message queues

  • API-first design

  • Seamless integration with third-party systems

2. Big Picture – Platform Overview

LIKE MAGIC connects key hospitality functions through an API- and UI-agnostic architecture:

Screenshot 2025-07-17 at 10.24.44 AM

3. Platform Infrastructure

Data Centre and Resilience

LIKE MAGIC’s platform is hosted in a world-class Google data centre in Zurich, leveraging Google’s industry-leading infrastructure to ensure robust and reliable service delivery. Key features include:

  • Robust Infrastructure: Built to the highest standards of physical security, environmental controls, and redundancy for continuous operation.

  • Advanced Backup and Disaster Recovery: Comprehensive strategies and Google’s resilient infrastructure protect data integrity and enable rapid recovery.

  • High Availability: Redundant power, cooling, and network connectivity minimize downtime and maximize uptime.

  • Strong Security Measures: Multi-layered security with strict access controls, network protections, and ongoing audits.

  • Cloud and Offsite Backups: Data is securely backed up and replicated across Google’s global network to enhance resilience.

  • Proactive Monitoring and Incident Response: Continuous monitoring and rapid response protocols ensure minimal service disruption.

By partnering with Google’s Zurich data centre, LIKE MAGIC delivers a secure, reliable, and resilient platform experience.

Architecture Principles

LIKE MAGIC adheres to key modern architecture principles:
    •    Event-driven & microservice-based
    •    Low coupling, high cohesion
    •    Business capability–driven service design
    •    Auto-scaling, evergreen component lifecycle
    •    End-to-end observability & traceability
    •    Platform as a Service (PaaS) operation model

All services are designed to be independently deployable and resilient by design.

Screenshot 2025-07-17 at 10.26.22 AM

4. Microservices & Connectors

Microservice Design:

  • Stateless

  • Self-contained

  • Horizontally and vertically scalable

  • Idempotent API operations

  • Contract-first interfaces

  • Supports async processing with eventual consistency

Screenshot 2025-07-17 at 10.32.04 AMConnector Principles:

  • Fallback integrations (e.g., local + real-time API)

  • Resilience with exponential backoff retry mechanisms

Connectors are technology-specific (e.g., PMS APIs, door lock APIs) and can be developed by LIKE MAGIC or external partners using the published OpenAPI specifications.

5. Integration Principles

  • Technology-Specific Connector Design
    Integration connectors are defined based on the functional scope of the underlying technology (e.g., property management systems, door access systems). Each connector adheres to the specific API contracts of the target system.
  • Contract-First Approach
    All integrations follow a contract-first methodology:
    • API specifications are defined before implementation.
    • Implementation may be carried out by LIKE MAGIC or the respective technology vendor.
    • Operation and maintenance can be handled by LIKE MAGIC or a trusted third party.
    • All contracts are documented and maintained as OpenAPI specifications to ensure transparency, consistency, and developer enablement.

6. Semantic Domains

The platform defines clean domain boundaries to ensure consistency across services. These semantic domains span reservations, profiles, operations, and payments—creating a shared language across APIs and analytics.

Screenshot 2025-07-17 at 10.42.32 AM

7. Processes - Self-Service Guest Journey

The platform supports a complete self-service flow:

  1. Booking & Pre-arrival

  2. Digital Check-in

  3. Digital Key Activation

  4. In-stay Communication & Upsell

  5. Digital Check-out & Feedback

Screenshot 2025-07-17 at 10.43.58 AMAll these steps are accessible through a responsive browser app - no downloads or self service kiosk dependencies required.

8. Conclusion

The LIKE MAGIC platform is engineered to deliver a modern, resilient, and guest-centric digital experience across the hospitality journey. By combining event-driven architecture, scalable microservices, and open integration principles, properties gain full control over their operational ecosystem while ensuring flexibility for future innovations. Through seamless connectivity, robust infrastructure, and a contract-first integration approach, LIKE MAGIC enables hotels to enhance efficiency, elevate guest satisfaction, and adapt rapidly to evolving market demands — all while maintaining data integrity and ownership.