Getting start
Following document are related to Bookings ONE On-premise installation, if you are using Cloud subscription plan of Bookings ONE, you do not need to refer to the following information
Install bookings ONE Server
1. Understand the components for the Bookings ONE Server
Bookings ONE server are builded based on Docker technology. Thanks for the Docker, Bookings ONE are able to hosting in various environments, and it can also support simple installation. At the beginning, you need to know the 3 key component to build up a Bookings ONE Server.
- Application - a docker container to host the Bookings ONE image
- Database - to save the key data on Bookings ONE
- File Storage - to save the videos and images upload to Bookings ONE, and the application log file
2. Choose the infrastructure based on your actual usage
You need to confirm the infrastructure, there are serval infrastructures we suggest in following for your reference:
If you have a strong knowledge on Docker hosting / Database / Cloud hosting, actually you can host into other platform such as (Google cloud / Alibaba Cloud) as you want.
3. Install the components
Finally, if you confirm the infrastructure, you can follow the below installation guideline to setup the system based on the component you choose:
Application
Data backup
If you are using Bookings ONE, we strongly recommend you to apply the backup to the Bookings ONE, but actually not all component need to backup by Bookings one.
Application - No need to backup the application. Bookings ONE docker image are built into a single image, no data will be stored in the application. If the application server fail on any reason such as hard disk damage, just reinstall the application server as a new one and connect to existing file storage and database.
Database - Strongly recommended, All the key user items and data are stored into the Bookings ONE Server, it will have a unrecoverable impact to the system if database data lost. Of course, there will have no specification on the backup policy and mechanism, hard-disk backup / RAID 1 data mirroring / database backup are all applicable for database back-up.
File Storage - Recommended, the files stored in Bookings ONE system are mainly the room image / photo, and the logging file to tracing the problem. The damage of the file storage due to the file lost may be caused some inconvenience to the Bookings ONE, such as image cannot be shown, but this will not have the direct impact of the main booking flow. User can easily re-upload the files to Bookings ONE to recover it. But we will still recommend you to have a file storage backup mechanism, since it will prevent the inconvenience to the end user when any unexpected issues happen.
System capacity suggestion
After you confirm the system infrastructure backup mechanism, next step you need to know are the capacity of each items.
The following suggestions of the system are based on the Bookings ONE previous production experience, which can handle 1000 User access and with the data storage, to ensure system’s stability and smoothness.
These suggestions are for estimate purpose only, system usage will be different depends on the usage frequency and features used. Please monitor the system resource usage and modify the system capacity based on the actual usage.
Application
| Cloud | On-premise | |
|---|---|---|
| min number of server/instances | 2 instances | 2 servers |
| min CPU | 8 Cores | 8 Cores |
| min RAM | 14 GB | 16 GB |
| min disk size | 10 GB | 50 GB |
Database
| Cloud | On-premise | |
|---|---|---|
| min DTU | 100 | - |
| min CPU | - | 8 Cores |
| min RAM | - | 16 GB |
| min disk size | 30 GB | 50 GB |
File Storage
| Cloud | On-premise | |
|---|---|---|
| min disk size | 10 GB | 30 GB |
Backup Server
Back up server storage estimation is based on a simple calculation. For example, if you want to keep daily backup for 30 days, monthly backup for 1 year and yearly backup for 7 years, the size required will be (30 + 12 + 7) * 30GB = 1.47 TB