Imagine that you want to design a tennis booking system. You have 5 tennis clubs who do not have an online API, which allows you to book a court, if you are booking a court or not: You have to make this part too.
Every time you want to bookmark that you want it to be known by our system. Perhaps using a post request form tennis partner on our server.
Every time our website is booked, we want to send the booking to our system. The difficulty is that their system should be accessible online and from the outside. IP can change, we have to use a DNR adapter.
If they are not available in their system, then we still accept booking and fallback in an asynchronous email, 'I confirm booking bookings' club.
I think the whole process is very complicated and was thinking about the online hotel booking system and hotel work. Do they have their data open and online?
The good thing is that the data will grow and will not fit well for any SQL;) such as sofa db
Here are many questions, I should try every one ...
Since it is an Internet application, using the built-in HTTP protocol Kind feelings arise. This form can be done through posts, retrieve, or even presenting some custom data structure. In the end, the exact approach to using will need to reduce the size and complexity of the information. Many architectures employ these methods and often combine them with encrypted, signed, and / or encoded payloads for security. A brief decline to consider with these methods is that they will need to communicate clearly to you about all the request / response message formats, regional boundaries and variations, because these mechanisms are not actually self-describing . On the other hand, these patterns use a very common protocol, easy to understand, easy to implement, and usually depend on the wire.
In contrast, architecture with very complex structures is often governed by WSDL web based services, general standards, it describes itself, is naturally the version, though they have more time to apply and Energy can take many benefits for web services that are operated by several WS- * standards which may be further investigative in your case.
For the process of reservation ... Many similar architectures will work in an orchestration model such as:
- Search for open booking spaces
- Make reservations for booking placements keep a deadline lock at this place, while the requestor fills all the necessary booking information. This race against the conditions which could cause multiple bookings for one place
- Once all the necessary booking information has been received and confirmed that the booking has been confirmed and Acceptably locked from the use by other requesters
For the SQL-style DB comment, I can not really tell that the amount of information supplied has been given. He said, my tendency tells me that the SQL-style DB is perfectly appropriate for the set of this problem. I have databases with many padabytes and there is a lot of SLA. I have included the need for high availability and the SQL-based database has proven support for some decades in this area.
Hope it helps.
Comments
Post a Comment