Welcome to the Java RESTful API test

The objetive of this test if to help us evalute your skills with:

• Problem Solving
• Web Server API Design
• Request-time data manipulation
• Testing strategies
• Deployment

Instructions

• Fork the repo into a private repo.
• You will need Gradle
• You can import the build.gradle file directly on your preferred IDE
• Spring Boot should be used to complete the test, although, if you feel you want to use something different, feel free
• Implement the required API endpoints.
• Implement a front-end to be able to create users and show them.
• Bonus point: show a map where location of each user is shown.
• Let us know when you have finished.

Tasks

The idea here is for us to see how you design a minimalistic API. This API will be used to perform CRUD operations on a model called User.

You're free to design this model as you want, but, at a minimum should have:

• ID
• First name
• Last name
• Latitude
• Longitude

Check the UserController file, there you'll see you have to fulfill the following empty edges:

    @RequestMapping(method = RequestMethod.GET, value="/jrt/api/v1.0/users")
    public Collection<User> users() {
        /**
         * Update this to return a json stream defining a listing of the users
         * Note: Always return the appropriate response for the action requested.
         *
         */
        //TODO: Implement this
        return null;
    }

    @RequestMapping(method = RequestMethod.GET, value="/jrt/api/v1.0/user")
    public ResponseEntity<?> get_user(@PathVariable String userId) {
        //TODO: Implement this
        return null;
    }

    @RequestMapping(method = RequestMethod.POST, value="/jrt/api/v1.0/user")
    public ResponseEntity<?> add_user(@RequestBody User input) {
        /**
         * Should add a new user to the users collection, with validation
         * note: Always return the appropriate response for the action requested.
         */
        //TODO: Implement this
        return null;
    }

    @RequestMapping(method = RequestMethod.PUT, value="/jrt/api/v1.0/user")
    public ResponseEntity<?> update_user(@PathVariable String userId, @RequestBody User input) {
        /**
         * Update user specified with user ID and return updated user contents
         * Note: Always return the appropriate response for the action requested.
         */
        //TODO: Implement this
        return null;
    }

    @RequestMapping(method = RequestMethod.DELETE, value="/jrt/api/v1.0/user")
    public ResponseEntity<?> delete_user(@PathVariable String userId) {
        /**
         * Delete user specified with user ID and return updated user contents
         * Note: Always return the appropriate response for the action requested.
         */
        //TODO: Implement this
        return null;
    }


    @RequestMapping(method = RequestMethod.GET, value="/jrt/api/v1.0/distances")
    public String distances() {
        /**
         * Each user has a lat/lon associated with them.  Determine the distance
         * between each user pair, and provide the min/max/average/std as a json response.
         * This should be GET only.
         *
         */
        //TODO: Implement this
        return null;
    }

This should be self-explanatory, we want you to fulfill the missing logic to generate expected responses.

It is important that you return correct response codes.

Notes

• The boilerplate code assumes you will use Spring.io and Spring Boot
• You must use Docker to provide working solution, feel free to use just a Docker file or docker-compose.yml
• We will test the app using Docker only, keep this in mind
• Indicate what testing approach are you using...TDD, write code and test later, mocking, and tell us how to test your code
• You already have a test folder for this with some boilerplate code
• Keep in mind we expect some level of authentication, not everyone should be allowed to access endpoints, keep it simple if you want to keep authenticated user in session cache that's ok
• Using MongoDB is required to store and retrieve data.
• For the distances endpoint, feel free to use any approach, there are several ways to do this
• Add a method to delete a User too
• For the views, you can use either React, Vue or Angular, your call.

Questions

• About the distances endpoint, please explain how would you scale this to hundreds and thousands of petitions per second, considering this is a CPU intensive endpoint.
• How would you approach this if latitude and longitude of user would be changing very frequently as well?

Deliverable

Publish your work in a GitHub repository. Feel free to modify this readme to give any additional information a reviewer might need. If you need more than 1 day to do this, you might be overthinking, feel free to add improvement notes in your README file, show-off there, we prefer better quality code if it takes longer, but you must justify this.