DEV Community

Cover image for How to use Google Places API with Caching ( complete Golang/React Source )
Stefan Wuthrich
Stefan Wuthrich

Posted on

How to use Google Places API with Caching ( complete Golang/React Source )

This day's I started with a new side-project named ProdutoMania

This project's main feature is to find products from my home country at the place I'm currently staying.
So I need a selector of location and to use Google Place/Maps API is on the hand.

Alt Text

Now, this API is paid as soon usage is getting above a certain amount.

This can be risky if you do put the queries as autocomplete/typehead directly fetching results on the client-side. So I decided to call backend API with a search term and the handler on the server-side take control of the usage of the API.

This opens the possibility to do throttling (not part of this post) and caching. Caching makes much sense, as locations do not change every minute, hour, not even days.
There is a max period of time allowed by Google for caching, at the time of writing this post it was 30 days.

To build the API I use:

  • Go with Chi Router (could also be done without, just using net/http standard package)
  • Google's official Go Client for Google Maps
  • Caching Middleware victorspringer/http-cache

Victor Springer's Caching Middleware is a perfect fit to cache RESTful API's. It supports memory, Redis, DynamoDB, and other storage for the cache.

here the config part of the story:

// Cache Middleware Config
memcached, err := memory.NewAdapter(
if err != nil {
cacheClient, err := cache.NewClient(
    cache.ClientWithTTL(24 * time.Hour),
Enter fullscreen mode Exit fullscreen mode

Then I define the handler and routes applying the middleware:

// Cache Google Place API calls
hLocation := http.HandlerFunc(handler.GetLocations)

r.Route("/", func(r chi.Router) {

// location autocomplete
r.With().Get("/{term}", CacheClient.Middleware(hLocation).ServeHTTP)

Enter fullscreen mode Exit fullscreen mode

On Frontend Side I use:

The Debouncing is important for the typeahead function to not call API on every onChange triggered by a Char. It also does not make sense to send just one char to API.

here the useLocation Hook/Service part of code:

export function useLocation() {
  const [{ isLoading, error, data }, dispatch] = useReducer(
  const fetchLocationResults = debounce(
    async (searchString) => {
      if (searchString.length > 2) {
        const locationUrl = `http://localhost:9090/${searchString}`
        dispatch({ type: actionTypes.FETCH_REQUEST })
        try {
          const response = await axios.get(locationUrl)
            type: actionTypes.FETCH_SUCCESS,
        } catch (error) {
          dispatch({ type: actionTypes.FETCH_FAILURE, error })
    { wait: 400 }
  return { error, isLoading, data, fetchLocationResults }

Enter fullscreen mode Exit fullscreen mode

You can get the full source to check the details:

Have fun (without high invoice from Google :-) )

Top comments (0)