Level 27
Better to save to DB first.
- If you pull direct from API when frontend reloads, you will easily hit the limit of the API (Assuming there is a rate limit)
- Frontend can also be slow if your API is slow, resulting in poor user experience
Apr 26, 2021
3
Level 2
Consuming API directly or saving into Db first
I am creating a betting site that i have to poll for updated data even every 5 seconds interval. So now i want to think of the best way between fetching data from api then save in db then front-end gets data from my db. Or i get the data directly from api to front-end. Which can be the best way.
Level 73
I would most likely fetch the data from the api with a job and then let the frontend get it from an internal api call from the database.
However do you really need to store it in your db if you fetch it from an api?
Level 80
@prido I know of a large betting site in the UK that would pull in odds, and then save them as a cached JSON file. The reason being, it’s infinitely quicker to read some JSON from memory than it is to query a database and fetch results. Especially if we’re talking about a lot of rows, or a lot of frequently-updated data.
Please or to participate in this conversation.