Then there is a very long long test that consist of 4 tasks: ## Task 1 * Write a new Controller. * Decide on your own how the methods should look like. * Add new Entities and ## Task 2 First come first serve: One Entity can be selected by exactly one other Entity with some condition. If this condition is not met you should throw an Exception. ## Task 3 Make use of the filter pattern to implement an endpoint in a Controller to get a list Entities with specific characteristics. Reuse the characteristics you implemented in task 1. ## Task 4 Security: secure the API. It's up to you how you are going to implement the security. The guidelines were as follow: * All new entities should have an ID with type of Long and a date_created with type of ZonedDateTime. * The architecture of the web service is built with the following components: * DataTransferObjects: Objects which are used for outside communication via the API * Controller: Implements the processing logic of the web service, parsing of parameters and validation of in- and outputs. * Service: Implements the business logic and handles the access to the DataAccessObjects. * DataAccessObjects: Interface for the database. Inserts, updates, deletes and reads objects from the database. * DomainObjects: Functional Objects which might be persisted in the database. * TestDrivenDevelopment is a good choice, but it's up to you how you are testing your code. The tell you that you have about a week to solve it, but you wouldn't need longer than 2-3 hours.