News for hackers. Stuff that matters.
Re:How We reduced our Google Maps API cost by ant6n on Saturday April 04, 2020 @04:27AM (#22776979)
Does it matter whether google or the consumer of the google api caches data?
Re:How We reduced our Google Maps API cost by lrem on Saturday April 04, 2020 @04:34AM (#22776998)
Placement of the cache definitely matters, even more so if you can take advantage of the more specific data freshness requirements.

Disclaimer: I work in Google. But I also worked a bit on effects of cache placement in my PhD.

Re:How We reduced our Google Maps API cost by boojing on Saturday April 04, 2020 @04:56AM (#22777075)
Why is the fact that you work at Google and have researched caching for your PhD a disclaimer? I fail to see how it denies your previous statement
Re:How We reduced our Google Maps API cost by lrem on Saturday April 04, 2020 @08:40AM (#22777896)
Actually dataflow is right, I should have written "disclosure". Which I am contractually obliged to in all discussions relating to Google.

Then, I might be perceived as biased due to that employment. I might even be actually biased. Better disclose that up front.

Re:How We reduced our Google Maps API cost by mehrdadn on Saturday April 04, 2020 @05:06AM (#22777120)
People say "disclaimer" when they mean "disclosure" for some reason.
Re:How We reduced our Google Maps API cost by ptsneves on Saturday April 04, 2020 @05:16AM (#22777157)
Because it is argument of authority, that he works with the subject company and has subject matter expertise. Take it however you will
Re:How We reduced our Google Maps API cost by arpa on Saturday April 04, 2020 @06:16AM (#22777391)
Caching responses might be against ToS, at least with Maps API, AFAIR, you are not allowed to cache (some of?) the results.