1. Introduction
10m

Workshop overview

Learn how implementations can be scaled across multiple teams and complex development environments. Using Enterprise, we'll sample a big menu of the latest features, including: auth, , coprocessors, safelisting and more!

What you'll learn

  • Authentication and authorization
  • Federated s
  • Coprocessors
  • limits
  • and safelisting
  • Schema update proposals
  • Caching

Who this workshop is for

API developers who have a basic understanding of .

  • Workshop slides

What we're building

KBT Threads Logo

KBT Threads has been a successful brick and mortar store dating back to 1972 with a focus on outdoor sports and adventure clothing. While KBT Threads has a long successful history, we have been struggling against our more digital-native competitors. We have invested in several digital channels including web, iOS and Android apps, and store pick-up options.

To support these new channels in a performant and scalable way, we have been building and a in our pre-production environments. We have spent time testing and validating this strategy and a decision has been made that this will be our go-forward API strategy.

Leadership is excited to move forward and wants to migrate this to the production environment and immediately begin routing traffic to it.

We, the engineering team, have pushed back on moving to production immediately. This graph is functional, but it is not production-ready. We have work to do to ensure that our is secure, performant, and scalable for all the use cases here at KBT Threads. It is now up to us to get this graph production-ready!

Getting started

Step 1: Create a Github repo

  1. Login to GitHub.

  2. Open up the workshop repository. This is the we will be hardening for this workshop.

  3. Select "Create a new repository", as shown below:

    Creating a new repository

  4. In the Create new repository setting, make sure these are set correctly:

    • Create the new repository in the Summit-Enterprise-Workshop. If you don't see this organization, please ask for help.
    • The workshop is set to Public.
  5. Name your repository with the following name format: <githubid>-graph.

  6. Click "Create your repository".

Clicking Create Repository

Task!

Editing files in GitHub

To keep things simple for this workshop, we recommend that you perform all edits directly in GitHub. To edit a file, navigate to that file and click the pencil icon in the top right corner.

Editing a file through github pencil icon

Once you're done editing a file, click the "Commit changes..." button.

Github comitting changes

Step 2: Login to GraphOS

We're using to build, manage and evolve our . is the web UI we'll be using to interact with our graph.

  • If you don't have an Apollo account yet, you'll be prompted to create one.

  • If you are an existing Apollo customer, you will need to join with an email address not associated with your company's SSO login. Open the link in an incognito window and create a separate account using your personal email.

Studio login

Task!

Step 3: Query your graph

If the previous 2 steps were successful, you should see a in the Studio organization named with your GitHub ID.

  1. Find your graph and star ️ the current so you can find it easily next time.

    Starring your Graph on Studio

  2. Click on your .

    Homepage of Your Graph in Studio

  3. Navigate to the Explorer in the main navigation.

  4. Run the default ExampleQuery :

    Example Query
    query ExampleQuery {
    users {
    id
    }
    }
studio.apollographql.com

Test Graph with Example Query

If the query returns data, we are now ready to begin! 🙌 🎉

Task!

Up next

In the next section, we will be looking at how limits can help limit the type and shape of operations will be allowed on our .

Next