3 ms·

While I like the simplicity of the lookup table, I find myself in larger projects to have different backoffs for different upstream services. I'll have shorter

While I like the simplicity of the lookup table, I find myself in larger projects to have different backoffs for different upstream services. I'll have shorter ones for services that can degrade without a large impact to service results and longer ones for services that are critical for results. I would prefer to have one algorithmically generated call that is flexible vs multiple individual functions that have different lookup tables, or generating tables and passing them in each time.

fmbb 1y ago
You could have two lookup tables.
- VWWHFSfQ 1y ago
  what if you have 100 lookup tables
  - barbazoo 1y ago
    Careful, that’s awfully close to N. /s
  - mceachen 1y ago
    If you don’t have lookup tables for your lookup tables you aren’t doing it right
  - avinassh 1y ago
    you could use SQLite, store all of them
    - kstrauser 1y ago
      MongoDB is web scale.
deleted 1y ago
[deleted]
harpiaharpyja 1y ago
Generating tables is the way to go in that case. The flexibility you need, with the advantages of being data driven.
kiitos 1y ago
Backoff is a client-side behavior, so if you want to give different backoff behaviors to different classes of upstream services, you just define those backoff tables somewhere where the client can pick from them based on the target service it's trying to talk to.