dadikovi / race-timer Goto Github PK

And also if its started or not

See architecture diagram

Now the flow continues, which can lead to malformed JSON response:

{"error": pq: insert or update on table "participants" violates foreign key constraint "participant_group"}{"startNumber":10,"groupId":0,"raceTimeMs":-1}

See architecture diagram

What we need:

• Execution times by SQL query
• HTTP response times by request
• Number of stored results

It would be really nice to export those as prometheus metrics and display them on a Grafana board.

Create the Create segment endpoint from the architecture diagram, and implement the whole flow.

Eg. start button should be disabled if group already started.
This last part is blocked by #24

Its not on the architecture diagram, but it will be a low hanging fruit after the POST segments endpoint, and it will be useful for our admin client.

See architecture diagram

Here is a doc about the difference

See architecture diagram

Consider:

• GO routines
• Contexts with deadlines
• loadtesting