Periodically polling an API, are there alternatives?
I’m currently working on a service that is supposed to aggregate data from a number of APIs, unify the data, and offer it through another API to the users. I had a couple of ideas for solving this, but I’m not confident my best solution is the best possible solution.
Periodically polling an API, are there alternatives?
I’m currently working on a service that is supposed to aggregate data from a number of APIs, unify the data, and offer it through another API to the users. I had a couple of ideas for solving this, but I’m not confident my best solution is the best possible solution.
Periodically polling an API, are there alternatives?
I’m currently working on a service that is supposed to aggregate data from a number of APIs, unify the data, and offer it through another API to the users. I had a couple of ideas for solving this, but I’m not confident my best solution is the best possible solution.
Pattern for checking online service availability
I’m not sure that this is entirely on-topic, but I’ll try to make it so.
Pattern for checking online service availability
I’m not sure that this is entirely on-topic, but I’ll try to make it so.
Pattern for checking online service availability
I’m not sure that this is entirely on-topic, but I’ll try to make it so.
Polling more recent / active items more frequently
I’m setting up a service that is meant to query, via a rate-limited API, a number of posts in real-time. Now, some of these posts can be several months old, and they should really only be queried, say, a few times a day once they reach an age where they’re unlikely to see new activity: most of my queries should be spent polling new posts.
Is it true that for Observer Pattern to work, there probably is some polling mechanism underneath?
The short question is: is it true that for Observer Pattern to work, there probably is some polling mechanism underneath? (update: in a network situation)