cbrgm/introduction-to-adrs

A talk about Architecture Decision Records

⏳Year Progress (64.21 %)
███████████████████▁▁▁▁▁▁▁▁▁▁▁
_{Updated: Fri, 23 Aug 2024 00:10:24 GMT}

introduction-to-adrs's Issues

Blockchainification of poketransfers

Title Blockchainification of poketransfers

Date: 2022-11-07, Author: Mathias Wanzenberg, Patrick Langer

Status

• - Proposed
• - Accepted
• - Rejected
• - Deprecated
• - Superseded

Context

Funktionalität des Spiels muss Kundenwünschen angepasst werden, daher soll der Transfer von Pokémon unter Spielern nachvollzogen werden können.

Considered Options

• Blockchain
• NoSql-Datenbank
• bestehende Datenbank erweitern

Decision

Wir führen zusätzlich zum vorhandenen System eine Blockchain ein, um Transaktionen von Pokémon zwischen Spielen festzuhalten.

Consequences

• Bestehende Funktionen müssen nicht verändert werden.

• Zum normalen Abspeichern der Transaktion, muss der Transfer in der Blockchain festgehalten werden.

• Konsistenz der Daten zwischen Blockchain und bestehender Datenbanklösung.

• API muss erweitert werden, um Funktionalität anzubieten.

Setup new Requestresponse and structure

Send whole Pokemoninfos to user

Date: 2022-11-07, Author: Sebastian G.

Status

• - Proposed
• - Accepted
• - Rejected
• - Deprecated
• - Superseded

Context

We need more informations about a pokemon in one request to minimize the traffic in our system. In the old system we get requests for every statfamily of a pokemon and have to list the available stats in a seperate request, e.g. attack stats, defense stats, special attacks etc...
Now we have more bandwith and want to minimize the requests to our system.

Decision

We decided to send the whole entry and stats we got from one pokemon. For this Decision we changed the API version to v2, so the old api still exists and is downward compatible.

Consequences

As a result for this decision we have to operate two systems simultanious. this means in the beginning of the api v2 we have a bit more work to do, but after the roll-out the the time to maintain is nearly the same.
After the time of 6 month we have to cut off the old system and force the users to use the new system.
When the cut off of V1 is done we have reduced our traffic by more than 60%.
The risk we have after this decision is, users dont want to use our api anymore. This risk is moderate, because we are the biggest system in this market and have the best datasets of pokemon.