Apollo Client – Demystifying Cache Normalization

One thing I want to call out, and seems to be the case (based on my understanding of the client code?), Apollo client doesn't try to understand the query and make intelligent use of the normalized cache based on the actual query going to be made. For example:

  query profile(name: $name) {
    id, name, address
  }

  query profile(id: $id) {
    name, address
  }

If the second query never made before the first query, even if they access the same object, it needs to make the network call again for the second query.

However, once you made all the queries, the normalization process will make sure the object is always fresh and there is no need for the extra network trip.