Wrapper for http.Get that supports caching about cragcast HOT 1 OPEN

Excellent idea!

Here are a few design suggestions that could achieve this in a very simple manner:

1. The cache can be a map attached to the server, or some other struct.
   a. lat,lng is the key.
   b. note that maps are not thread safe, so we need to ensure we add proper mutex mechanics.
2. The forecast fetcher starts with the server, in a separate go routine.
   a. It continues running until the server receives a shutdown signal.
3. When a request comes in, we check the cache for a key.
   • if it doesn't exist, call the noaa API
   • if it does, ensure the timestamp on the caches value is new enough (eg 1000 seconds)
     • if new enough, return cached value
     • if too old, call noaa API
4. All noaa requests made (due to cache miss or otherwise) always refresh the cache for the lat,lng (key).

Along with simplicity, a primary benefit is our API remains as is since the complexity around cache logic is buried into the implementation details retrieval. This is great for clients that don't need to understand where the data is coming from. We also no longer need to set TTLs with our http calls.

Here's a quick visual to make this idea a bit concrete (missing some nuance in the bullets above):

Let me know your thoughts!

from cragcast.