The API itself isn't mine, but the Premier League's - fpl is just a wrapper around it. I was thinking more along the lines of creating a function that saves the players to a database locally, but I'm not sure that how I can implement that and if that would work on every single operating system.
You are viewing a single comment's thread from:
On the other hand, I was thinking that in general terms we shouldn't struggle too much when it comes to retrieve data from a REST API, and I like REST by the way :)
Since I like REST too, in my humble opinion, that could be seen as kind of code smell in a sense that the API's architecture is not very well designed?
So, here are alternative scenarios (for PHP) to solve the problem of a slow REST API that requires too many operations to fetch the data:
Write your own API with REST improving the architecture of the original one -- I tried to do something similar to fpl at Data Driven Test Development Demo
Write your own API with GraphSQL -- GraphQL Demo for Symfony 4
In both cases, we're assuming that the API interface can be changed, and also it is okay to "scrap" and store the data on our side.
That's definitely something I will look into, thanks!
That makes sense. IMO, I'd suggest to implement a simple solution while observing if the results obtained are okay. What about REST API caching with HTTP headers? https://restfulapi.net/caching/