https://github.com/ffcactus/meeting-app
A demo for a pre interview...
https://github.com/ffcactus/meeting-app
Last synced: about 1 year ago
JSON representation
A demo for a pre interview...
- Host: GitHub
- URL: https://github.com/ffcactus/meeting-app
- Owner: ffcactus
- Created: 2021-07-01T08:26:57.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2021-07-03T07:04:04.000Z (about 5 years ago)
- Last Synced: 2025-06-29T18:01:56.365Z (about 1 year ago)
- Language: Java
- Size: 16.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# meeting-app
A demo for a pre interview.
Here are some tips for you to understanding the implementation.
* The test hope the code to be production ready, so it's not just a pure algorithm.
I try to write the code so that it can be quite easily changed to a real application.
* The implementation assumes the booking should be persistent, the application should be stateless.
So it has a **MeetingRepository** interface.
It assumes the **MeetingRepository** can be easily implemented by a SQL style database.
* It has a **sdk** package. It contains some generalized class. For example, a booking string is represented by a **Booking**.
a **MeetingService** provide APIs for stateless booking operations.
* It assumes that a booking can not across the midnight. So all the meetings are grouping by date. It can also reduce the calculation time and data loading time.
* In the example, the application seems to be processing a bulk of requests at once, and the booking requests are not in their submit time,
However, The **MeetingService** assume the request should come one by one. The sort to the requests happens in the unit test.