📘
Open Booking SDK
  • Implementation Options
  • Quick Start Guide
    • Design Considerations
    • StoreBookingEngine
      • Day 1: Fake Implementation
      • Day 2: Open data feeds
      • Day 3: Test data
      • Day 4: C1 and C2 without leases
      • Day 5: Leases and Booking
      • Day 6: Orders feed
      • Day 7: Cancellation
      • Day 8: Authentication
  • Reference
    • Dependencies
Powered by GitBook
On this page
  • Overall Objective
  • Introduction

Was this helpful?

Edit on Git
  1. Quick Start Guide

StoreBookingEngine

PreviousDesign ConsiderationsNextDay 1: Fake Implementation

Last updated 5 years ago

Was this helpful?

Overall Objective

This guide will help you implement StoreBookingEngine within a target development window of 8 days, creating an implementation of the .

Introduction

The StoreBookingEngine is essentially a number of abstract classes which can be implemented to create a fully operation Open Booking API.

The following are required for a minimal implementation:

  • Feeds - generate the RPDE feeds

  • Stores - methods to execute various booking operations that are executed by the StoreBookingEngine

  • IdComponents - customisable composite IDs to represent the key entities within your system

  • EngineConfig.cs - configuration of the StoreBookingEngine

  • Startup.cs or ServiceConfig.cs - initialisation

Additionally, the following are required to bind the StoreBookingEngine to the web framework:

  • Helpers - convert JSON requests to string, and responses to controller return types.

  • Controllers - call the StoreBookingEngine from the Open Booking API endpoints.

The and projects provides a good example of an implementation of StoreBookingEngine using a - which offers a fake implementation of a booking system backend.

BookingSystem.AspNetCore
BookingSystem.AspNetFramework
OpenActive.FakeDatabase.NET
Open Booking API
Example implementation of StoreBookingEngine