yefeiw / runningInfoSerivce

Simulated running information from NIKE health, using java spring boot

Running Information Analysis

This project implements the interaction of spring MVC and spring Data via spring boot.

Database Information

The implemented database is mysql in the following address: jdbc:mysql://localhost:3306/running_information

username:root

password: root

Test The Project

1. Open mysql via either docker-compose or installed version. Remember to to the following:

(in mysql console)  create database running_information

2. build and install

mvn clean install
cd target
java -jar running-info-service-1.0.0-SNAPSHOT.jar

3. Do the following in postman:

• Note: all transactions under localhost:9000

POST: /add
[
 {
 "runningId": "7c08973d-bed4-4cbd-9c28-9282a02a6032",
 "latitude": "38.9093216",
 "longitude": "-77.0036435",
 "runningDistance": "39492",
 "totalRunningTime": "2139.25",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross0",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 },
 {
 "runningId": "07e8db69-99f2-4fe2-b65a-52fbbdf8c32c",
 "latitude": "39.927434",
 "longitude": "-76.635816",
 "runningDistance": "1235",
 "totalRunningTime": "3011.23",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross1",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 },
 {
 "runningId": "2f3c321b-d239-43d6-8fe0-c035ecdff232",
 "latitude": "40.083824",
 "longitude": "-76.098019",
 "runningDistance": "23567",
 "totalRunningTime": "85431.23",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross2",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 },
 {
 "runningId": "28810a26-25e6-4680-8baf-59bb07c4aee0",
 "latitude": "42.957466",
 "longitude": "-76.344201",
 "runningDistance": "11135",
 "totalRunningTime": "98965",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross3",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 },
 {
 "runningId": "fb0b4725-ac25-4812-b425-d43a18c958bb",
 "latitude": "38.5783821",
 "longitude": "-77.3242436",
 "runningDistance": "231",
 "totalRunningTime": "123",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross4",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 },
 {
 "runningId": "35be446c-9ed1-4e3c-a400-ee59bd0b6872",
 "latitude": "42.375786",
 "longitude": "-76.870872",
 "runningDistance": "0",
 "totalRunningTime": "0",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross5",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 },
 {
 "runningId": "15dfe2b9-e097-4899-bcb2-e0e8e72416ad",
 "latitude": "40.2230391039276",
 "longitude": "-76.0626631118454",
 "runningDistance": "0.1",
 "totalRunningTime": "0.1",
 "heartRate": 0,
 "timestamp": "2017-04-01T18:50:35Z",
 "userInfo": {
 "username": "ross6",
 "address": "504 CS Street, Mountain View, CA 88888"
 }
 }
]

GET: running/<page_number>

POST: remove/<runningId>

Comments

• DELETE may make more sense than POST, I have tested both and decided to use POST for simplicity.

• GET is guaranteed to return the sorted paged results. However, the sorting is done in the pageRequest. The database query is to get all with heartRate > 59. I understand that there should be another approach to sort in the query. I am interested in learning the differences.