Differences

This shows you the differences between two versions of the page.

--- librematch:design:architecture:start [2022-10-28 01:26] – [Example (Bright Sky)] nimda
+++ librematch:design:architecture:start [2022-10-28 01:27] (current) – [LibreMatch] nimda
@@ Line 22: / Line 22: @@
 {{ ::librematch-arch-draft.png?400|}}
-Basically we should poll the Relic Link API endpoints for all data every so many seconds (this time is our minimum latency for our whole system).
+Basically, we should poll the Relic Link API endpoints for all data every so many seconds (this time is our minimum latency for our whole system).
 So the time frame in which we see certain information (Match infos, wins of games) and could deliver information to our API.
-Then we parse the results into a data structure of ourselves to make error handling easier and also deal with types of data and not handle everything as a huge JSON-Array that is being exposed by the Relic Link API. This data we send to the database which is our persistence layer. From our persistence layer we are able to request data for our endpoints that we expose to the users.
+Then we parse the results into a data structure of ourselves to make error handling easier and also deal with types of data and not handle everything as a huge JSON-Array that is being exposed by the Relic Link API. This data we send to the database, which is our persistence layer. From our persistence layer, we are able to request data for our endpoints that we expose to the users.
 Some endpoints may require a Pub/Sub API (e.g. live updates for match information), some are fine with the usual REST-API approach.
 {{:librematch:librematch_2022-10-09_3_.jpg?600|}}