Multiple formats supported by all platforms. You can install it on different platforms and configurations.
Our proposal is disruptive and innovative. The data distribution through Virtual Appliances (VAPPs) is common in other sectors, but not in the holiday rental sector.
A good strategy to implement us into a foreign system can be a search based on providers meaning: you current system makes a search like always and when it ends the system calls our LCVAPP API
search and merges the results (it's a JSON containing all the data you may need) to show it into the search result front.
If you access our raw data that is stored under our model you will need to understand how we work, what all the concepts are and how to calculate prices with discounts and implement all the rules for a booking in your platform.
It probably will collide with your existing data structure, so you need to develop translators and bother with maintaining the data up to date and be sure that you aren't mistaking any concept.
In the other hand, if you use the LCVAPP solution, it will give you everything already calculated with the price already there for that stay and you only need to merge this JSON with your already existing search response.
You should have it on your servers to save on resources. You don't have to worry about the integrity of the data you receive, or if the data are being treated correctly, because the machine do it for you. If you are on our servers, anything you do will have to go through the internet, and this process will take time and money. If the machine is running on your servers, they are internal resources, so there is no cost. Besides, searches are realized on your system, so there are no connectivity failures.
All you need to do is give permissions to the LCVAPP to connect to LaComunity servers and give your servers permission to connect to the LCVAPP. The machine does not connect to anything, the only access point it has is LaComunity. It is an isolated and safe system.
You can create as many virtual machines as you need and put a load balancer in front of them to distribute the requests between them.
The data is already inside the LCVAPP, therefore you are saving the work of download all the data base in your system. The LCVAPP is already the data base and the integration itself. It would be like having LaComunity on your system without having to download all the properties data into your system.
So far, the partner connects to LaComunity, download all accommodations and keep them in their system. This means a job of understanding the business rules and writing the code to be able to download the LaComunity properties. This is time and work for the partner. LaComunity proposes an alternative to avoid this. We send a package that already has all the properties and only has to be coupled to the system of the partner. When a search enters, the partner only has to redirect it to the LCVAPP, without having to do any integration. Just download and run the LCVAPP without having to save the data base in the partner system. If LaComunity make any change, the LCVAPP is updated inmediatly and the partner have not to do any development to have the change updated. All updates are automatic. This process save time and work.