---
title: "Discussion on \"Four ways I tried to ingest data for my League of Legends hobby project\" | Hashnode"
description: "Discussion on \"Four ways I tried to ingest data for my League of Legends hobby project\". Riot API has no endpoint for matches by rank. Four approaches I tried to ingest League of Legends games with 200 match calls a minute, and what worked"
url: "https://hashnode.com/posts/four-ways-i-tried-to-ingest-data-for-my-league-of-legends-hobby-project/6ad0eecd4a7b5c5922cff377"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Four ways I tried to ingest data for my League of Legends hobby project](https://siont-dev.hashnode.dev/four-ways-i-tried-to-ingest-data-for-my-league-of-legends-hobby-project?utm_source=hashnode&utm_medium=feed)

Riot API has no endpoint for matches by rank. Four approaches I tried to ingest League of Legends games with 200 match calls a minute, and what worked

Oct 15 · 9 min read · siont-dev.hashnode.dev  
Read the article

-   [#api](https://hashnode.com/tag/api)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#data-engineering](https://hashnode.com/tag/data-engineering)
-   [#side-project](https://hashnode.com/tag/side-project)
-   [#gaming](https://hashnode.com/tag/gaming)
-   [#leagueoflegends](https://hashnode.com/tag/leagueoflegends)

## Written by

[Siont](https://hashnode.com/@siont)

@siont · Berlin

  
[View profile](https://hashnode.com/@siont)

## Responses 3

Markdown supported · ⌘↵ to post

[Praneet Brar](https://hashnode.com/@praneetbrar)

[Oct 20](https://hashnode.com/posts/four-ways-i-tried-to-ingest-data-for-my-league-of-legends-hobby-project/6ad0eecd4a7b5c5922cff377/comment/6ad75b30ae3cf9075c9740a7)

using the almost free ladder calls to decide where to spend the expensive match calls is a really neat trick, 38 to 62 useful calls out of 100 is a clear win. now that you re-read every 2 hours instead of 30 minutes, do you lose many players who play a few games and then drop division in between?

[Siont](https://hashnode.com/@siont)

[Oct 20](https://hashnode.com/posts/four-ways-i-tried-to-ingest-data-for-my-league-of-legends-hobby-project/6ad0eecd4a7b5c5922cff377/comment/6ad75b30ae3cf9075c9740a7#reply-6ad767c773c0169adf023389)

Thanks for the question! I just checked the data as it's a very interesting point. When we re-read the ladder in 2 hours - about 84% players are still on the same page and 16% are moved to the other division. We're storing their games per-player, not per-page, so they can pop up on other pages we read, but this depends on luck as we're not reading all pages. But even if we're loosing those players - we still don't loose games because after each pass most servers still have 15–40k players waiting with new games, far more than our match API limit can fetch, so losing some just means picking someone else

[Praneet Brar](https://hashnode.com/@praneetbrar)

[Oct 21](https://hashnode.com/posts/four-ways-i-tried-to-ingest-data-for-my-league-of-legends-hobby-project/6ad0eecd4a7b5c5922cff377/comment/6ad75b30ae3cf9075c9740a7#reply-6ad8a9b4c076f6af04cc2b26)

84% still on the same page after 2 hours is higher than i'd have guessed, so most of a full re-read is just confirming nothing moved. are the 16% that move mostly near the top of the ladder or spread all over?