Ah given my Google oauth token has a TTL of approx 3600s, i would attach something like this to my f
Ah given my Google oauth token has a TTL of approx 3600s, i would attach something like this to my fetch request and it should ~roughly reduce some request load given a worker in the same data center is executed?
cf: {
// Always cache this fetch regardless of content type
// for a max of 5 seconds before revalidating the resource
cacheTtl: 3400,
},
This is for a project operating at very small scale, think a request load of ~ <= 125/month on average hitting this api endpoint and thats an estimate on the high side -- i don't want to inject the complexity of a full blown db in this case
I would probably be fine with just refreshing the google oauth tokens as well on every request but don't mind understanding if there are some optimizations Cloudflare provides for cases like this
cf: {
// Always cache this fetch regardless of content type
// for a max of 5 seconds before revalidating the resource
cacheTtl: 3400,
},
This is for a project operating at very small scale, think a request load of ~ <= 125/month on average hitting this api endpoint and thats an estimate on the high side -- i don't want to inject the complexity of a full blown db in this case
I would probably be fine with just refreshing the google oauth tokens as well on every request but don't mind understanding if there are some optimizations Cloudflare provides for cases like this
