Recipe API assessment for AA bank. This is an assessment of users can organize their recipes.
The problem and its solution are explained.
Create a standalone java application which allows users to manage their favourite recipes. It should allow adding, updating, removing and fetching recipes. Additionally users should be able to filter available recipes based on one or more of the following criteria:
- Whether or not the dish is vegetarian
- The number of servings
- Specific ingredients (either include or exclude)
- Text search within the instructions. For example, the API should be able to handle the following search requests: • All vegetarian recipes • Recipes that can serve 4 persons and have “potatoes” as an ingredient • Recipes without “salmon” as an ingredient that has “oven” in the instructions.
Please ensure that we have some documentation about the architectural choices and also how to run the application. The project is expected to be delivered as a GitHub (or any other public git hosting) repository URL. All these requirements needs to be satisfied:
- It must be a REST application implemented using Java (use a framework of your choice)
- Your code should be production-ready.
- REST API must be documented
- Data must be persisted in a database
- Unit tests must be present
- Integration tests must be present
Created a standalone java application that allows users to manage their favorite recipes. Each user has own favorite recipe. I used Java 11, Spring Boot, and Maven to implement this assignment. A short description of my solution and explaining some design decisions, you can find here
We have 2 different users. Mahdi and Alex are our users here. Mahdi can manage his list without effect on Alex's favorite list. My assumptions when solving the challenge, you can find here
To clone and run this application, you'll need Git, Maven, Java 11. From your command line:
- A short explanation about how to run the solution with all the needed parts, you can find here
For handling this assignment At least we need 2 entities. One use can't have 2 recipes with one title.
Provided three endpoints for handling, recipes, ingredients, and users. First of all user needs to get Bearer token to call other services.
- Get a Bearer token from /v1/users/login API.
- Pass this token as a parameter 'Authorization:Bearer Bearer eyJhbGc...' to HTTPie request.
- A file explaining what needs to be done to use the service, please find it here
There is a to-do list with things I would add if I have more time and explaining what is missing and why. Please find it here
Give your username '/v1/users/login' and get the Bearer Token,Then click on Authorize button at the up right of the page. Paste the token here. At last click on 'Authorize'
Provided 61 tests(Unit test, Integration test, and End-to-end test)
- 100% Class
- 95% Method
- 91% Line
- Swagger
- Run test
mvn test - Postman. There is a Postman file of this project in this path located here
- CLI. Commands provided with HTTPie. *Note: A file explaining what needs to be done to use the service, you can find here
A description of how it will scale when the number of users grow, you can find here
- You can find diagrams in path here
- A short description of the solution and explaining some design decisions, you can find here
- A short explanation about how to run the solution with all the needed parts, you can find here
- A file explaining what needs to be done to use the service, you can find here
- A to-do list with things I would add if I have more time and explaining what is missing and why, you can find here
- My assumptions when solving the challenge, you can find here
- A description of how it will scale when the number of users grow, you can find here