• 1 Post
  • 273 Comments
Joined 2 years ago
cake
Cake day: March 25th, 2024

help-circle

  • I used to upgrade every 2 years until I got an iPhone 15 Pro. I was going to ride or die with my 13 mini but I really wanted to get all my devices on usb-c. I splurged on my current phone with the intention to keep it for a long time. Going on 3 years now.

    I used to go hard on the androids with rooting and customizing. I’ve since resigned myself to wanting a phone that “just works.”


  • I’ve been in a similar situation, and what I wound up doing was what you describe as a “catch up” job. I do as much work as I can before I can’t anymore, store the result, and then continue from the failure point at a later time. It does feel a bit disgusting with a lot more moving parts but you gotta get a little creative with unreliable APIs. Gotta be careful with this though, because if you try and run this catchup at the start of every new run of the job then you can see how the backlog could quickly grow impossibly large if you don’t allow requests to ultimately fail and drop out of the queue entirely.

    Also there’s not really anything you can do if the pagination methodology of the API is changed without warning. If the provider has some way to subscribe to API changes, like a newsletter, then you could get on that. Otherwise all you can really do is set up some alerting if you can reliably recognize when you’re only getting a partial data set.