10. Journey's end
2m

We took a shortcut to server-land with Apollo Studio, where we saw queries succeed and fail. Now how about we make sure the whole round-trip query journey works from our client app, to the server and back?

Let's run the client. Open up a new terminal and navigate to the client folder. Run npm start, which will open up your browser to localhost:3000.

Look at that, our Catstronauts app is showing all of the tracks on the homepage! Well done! Our query's journey is complete.

Screenshot of the Catstronauts homepage in a browser showing live data

Can you see all the cards displaying live data? What's the author's name on the last track card?

We've come a long way. We retrieved live data from a REST API. We used a RESTDataSource to handle making these API calls more efficient. We created a resolver to connect to that data source and successfully return the correct fields to our client. We even saw what can happen if our query went sideways and didn't follow the happy path. In the end we got all of the Catstronauts tracks on our homepage.

Have you noticed that we changed our data from mock objects to live data, without needing to modify a thing on the client app? Everything kept working as in Part 1, but now with real data.

Although things can and will change (new data sources, new clients, and so on), the data graph brings a new level of flexibility and resilience for developers. The single source of truth for your data that your clients can rely on, will remain the schema.

In the next course, we'll be using query arguments, writing more resolvers, and adding a new Track Details page to our Catstronauts app. See you there!

Previous