Holibob Docs

Event-Driven Architecture

Event-Driven Architecture

Our Event-Driven Architecture Features are designed to improve how our systems communicate and respond to changes in real time. By adopting this approach, different parts of our platform can react to key events such as bookings, cancellations, product updates, or availability changes without requiring direct connections between systems. This decoupling increases the flexibility, scalability, and reliability of the platform, while creating new opportunities for integrations, automation, and real-time responsiveness.

Key Benefits

  • Real-Time Responsiveness: Systems can react instantly to important events, ensuring up-to-date information and faster operations.

  • Flexible Integrations: Partners can connect their own systems to listen for relevant events, enabling seamless automation and data flows.

  • Scalable & Reliable: Decoupled architecture allows us to scale services independently and maintain high reliability, even as your business grows.

  • Operational Efficiency: Reduce manual processes and enable automated workflows triggered by platform events.

  • Future-Proof Foundation: Our shared patterns and best practices make it easier to add new integrations and use cases over time.

How It Works

  1. Event Emission: When something important happens on the platform (like a booking confirmation or a product update), an event is generated and published to our event delivery infrastructure.

  2. Event Delivery: We manage the infrastructure that delivers these events to interested systems, whether they are internal services or partner integrations.

  3. Partner Integration: We work with you to identify which events are valuable for your operations. You can then set up your systems to listen for these events and trigger your own workflows or automations.

  4. Decoupled Communication: Because systems communicate via events rather than direct connections, changes in one area do not disrupt others, making the platform more robust and adaptable.

  5. Best Practices: We are building a shared foundation of patterns and best practices to ensure event usage is consistent, reusable, and easy to adopt across different scenarios.

Partner Actions

  • Identify Relevant Events: Work with us to determine which events are most valuable for your business processes.

  • Integrate Systems: Set up your systems to listen for and respond to relevant events, using the integration methods we provide.

  • Review & Optimise: Collaborate with us to refine event usage and integrations as your needs evolve.

Additional Notes

  • Feature Availability: Event-driven features are being rolled out progressively; availability may vary depending on your integration needs.

  • Customisation: We can tailor event delivery and integration patterns to fit your operational requirements.