Add GraphQL Edge Caching to Swell

Add GraphQL Edge Caching to Swell

Swell is the customizable, API-first ecommerce platform designed for next-generation shopping experiences.

Just like Grafbase, Swell works with the tech you love. It doesn't matter if you're using React, Vue, Angular, REST or GraphQL, Swell fits right in.

Using the Swell GraphQL API we can connect it to Grafbase to benefit from:

  1. Speed — Get even faster responses and lessen server load with Grafbase Edge Caching.
  2. Flexibility — Combine data from multiple APIs effortlessly using Grafbase Edge Gateway.
  3. Savings — Stay within your API limits and save money.
  4. Insights — Monitor your data in real-time with Grafbase Analytics.

In this guide, we will focus on improving the performance of the GraphQL API by implementing Grafbase's GraphQL Edge Caching on top of the Swell GraphQL API.

You should already have a Swell store setup to follow this guide.

Begin by executing the following command inside a new or existing project's directory:

npx grafbase init --template graphql-swell

This command will generate a new folder grafbase in the root of your project.

Next, open the file grafbase.config.ts and make any adjustments.

By default, Grafbase will:

  • Add Swell as a data source
  • Cache all queries for 60 seconds
  • Enable public access to the Grafbase Edge Gateway
  • Forward Authorization and X-Session headers to Swell
import { config, connector, graph } from '@grafbase/sdk' const g = graph.Standalone() const swell = connector.GraphQL('Swell', { url: `https://${g.env('SWELL_STORE_ID')}`, headers: headers => { headers.set('Authorization', { forward: 'Authorization' }) headers.set('X-Session', { forward: 'X-Session' }) }, }) // Disabling namespace may cause conflicts with other connectors g.datasource(swell, { namespace: false }) export default config({ graph: g, cache: { rules: [ { types: ['Query'], maxAge: 60, }, ], }, auth: { rules: rules => { rules.public() }, }, })

Now update .env with your SWELL_STORE_ID value. You can find this from your Swell developer settings.

If you plan to add other data sources, you should enable the namespace to prevent schema conflicts.

If you'd prefer not to pass the Authorization header with requests from the client, you can also set the values to use an environment variable stored by Grafbase:

const swell = connector.GraphQL('Swell', { url: `https://${g.env('SWELL_STORE_ID')}`, headers: headers => { headers.set('Authorization', g.env('SWELL_API_KEY')) }, })

If you don't use header forwarding, make sure to add your SWELL_API_KEY value to the file .env:

SWELL_STORE_ID= # Only if you set the Authorization header with a static value # SWELL_API_KEY=

Finally, run the Grafbase development server by using the command below:

npx grafbase dev

You now have a GraphQL API running locally that acts as a proxy to Swell! 🎉

You can execute any GraphQL query or mutation you normally would with Swell using the new endpoint (locally):

Grafbase Pathfinder can be found at where you can explore the Grafbase Edge Gateway API and schema.

💡 Make sure to commit the grafbase folder with the rest of your application.

You can and should use the Grafbase CLI when building locally (or in a branch) to proxy your Swell store but you will need to deploy to Grafbase to take advantage of GraphQL Edge Caching.

Follow these steps to deploy to production:

  • Signup for a Grafbase account
  • Create a new project
  • Connect and deploy your application where the grafbase was added
  • Make sure to add your SWELL_STORE_ID when deploying, unless you made it optional
  • Update your host (Netlify, Vercel, Fly, etc.) with the new GraphQL API endpoint that Grafbase supplied for your new project.

That's it!

Grafbase is programmed to autonomously deploy a fresh gateway each time it identifies a change to grafbase.config.ts. Consequently, if you need to adjust any cache settings, including parameters like maxAge, staleWhileRevalidate, and mutationInvalidation, you're free to do so.

Grafbase will handle the rest of the process seamlessly. We'll explore extending the Swell API with custom fields in another post.

Get Started

Build your API of the future now.