Tech stack

• Java 8
• Spring boot
• Maven 3.3.5
• Docker
• Caffeine Cache
• Swagger
• Lombok

System requirements

An underwater volcano formed a new small island in the Pacific Ocean last month. All the conditions on the island seems perfect and it was decided to open it up for the general public to experience the pristine uncharted territory. The island is big enough to host a single campsite so everybody is very excited to visit. In order to regulate the number of people on the island, it was decided to come up with an online web application to manage the reservations. You are responsible for design and development of a REST API service that will manage the campsite reservations. To streamline the reservations a few constraints need to be in place -

• The campsite will be free for all.
• The campsite can be reserved for max 3 days.
• The campsite can be reserved minimum 1 day(s) ahead of arrival and up to 1 month in advance. Reservations can be cancelled anytime.
• For sake of simplicity assume the check-in & check-out time is 12:00 AM

System Requirements II

The users will need to find out when the campsite is available. So the system should expose an API to provide information of the availability of the campsite for a given date range with the default being 1 month. Provide an end point for reserving the campsite. The user will provide his/her email & full name at the time of reserving the campsite along with intended arrival date and departure date. Return a unique booking identifier back to the caller if the reservation is successful. The unique booking identifier can be used to modify or cancel the reservation later on. Provide appropriate end point(s) to allow modification/cancellation of an existing reservation Due to the popularity of the island, there is a high likelihood of multiple users attempting to reserve the campsite for the same/overlapping date(s). Demonstrate with appropriate test cases that the system can gracefully handle concurrent requests to reserve the campsite. Provide appropriate error messages to the caller to indicate the error cases. In general, the system should be able to handle large volume of requests for getting the campsite availability. There are no restrictions on how reservations are stored as as long as system constraints are not violated.

• Provide the info for the availability (1 months for default) - Endpoint.
• Provide an API to reserving the campsite. (user data - email - arrival and departure date. 3 days at max).
• Return a booking identifier.
• Search by booking identifier.
• Handle concurent requests.

How to run?

./mvnw spring-boot:run

Swagger URL after deploy locally

http://localhost:8080/api/swagger-ui.html