xilution-graphql-backend-example

An example demonstrating how to build a GraphQL backend using...

Xilution's IAM Suite (Elephant, Hippo, Rhino, Zebra)
Xilution's Data Storage Service (Beagily)
Xilution's API Hosting Service (Fox)

Time Requirement

I will take about thirty (30) minutes to run through this example.

Use Case

As: a frontend app builder who creates apps for multiple clients.

I want: a GraphQL enabled API that restricts access to only known users.

So that: I can build a pet data management app for one of my clients.

Xilution Product Hierarchy

Here's a quick overview of the Xilution products highlighted in this example. For a complete directory of Xilution products, see https://prod.products.xilution.com/.

                 +------------------+
                 | Xilution Account |
                 +--------+---------+
                          |
                          v
                   +------+-------+
                   | Organization +--------------+
                   +------+-------+              |
                          |                      |
                          v                      |
               +----------+----------+           |
               |    [ Elephant ]     |           |
               | Sub-Organization(s) |           |
               +----------+----------+           |
                          |                      |
                          v                      |
          +--------------------------------+     |
          |               |                |     |
          v               v                v     v
    +-----+-----+   +-----+-----+      +---+-----+---+
    | [ Hippo ] |   | [ Rhino ] |      |   [ Fox ]   |
    | Client(s) |   |  User(s)  |      | Instance(s) |
    +-----------+   +-----------+      +-------------+

When you create a Xilution Account, an Organization record is created for you. This is referred to as your "Account Organization" in the instructions below. As a frontend app builder who supports multiple clients, you can create multiple Sub-Organizations via Xilution Elephant. One for each client you support. This allows you to separate client resource management and billing from your Account Organization and other Sub-Organizations.

Xilution Hippo is part of Xilution's IAM suite and manages Sub-Organization clients. A client is a reference to a web or mobile application. In this example, you'll create one Sub-Organization client.

Xilution Rhino is part of Xilution's IAM suite and manages Sub-Organization users. In this example, you'll create one Sub-Organization user.

Xilution Fox is a managed API hosting solution that uses Docker to instantiate API server instances. You can associate Fox instances with your Account Organization and/or Sub-Organizations. In this example, you'll associated a Fox instance with a Sub-Organization.

Implemented Solution

When you complete this example, you will create a GraphQL enabled API that supports the use case mentioned above.

                                  +-----------+
                            +---->+ [ Zebra ] |
                            |     |   Auth    |
                            |     +-----------+
            +---------+     |
       o----+ [ Fox ] +---->+
    GraphQL |   API   |     |
            +---------+     |
                            |    +--------------+
                            +--->+ [ Beagily ]  |
                                 | Data Storage |
                                 +--------------+

The API authorizes calls to it's /graphql endpoint by making /oauth/authenticate calls to Xilution Zebra with the Bearer token included in the Authorization header of each request. Xilution Zebra is OAuth 2.0 compliant and is part of Xilution's IAM (identity and access management) suite and is used to authenticate and authorize Rhino users and Hippo clients.

The API interfaces with Xilution Beagily to store and retrieve Pet data. Xilution Beagily is a simple JSON data storage API that features integrated search and access control features. The API makes calls to Beagily with a Bearer token included in the Authorization header of each request. This token is separate from the token included in requests to the API's /graphql endpoint and is acquired by the API from Zebra using the credentials of a client referred to as API Client in the instructions below. Each Beagily record has an owning user and an access policy which is checked against a context generated by the access token to control access to records.

Features

Xilution's IAM Suite (Elephant, Hippo, Rhino and Zebra) for identity and access management.
Xilution Fox for API hosting.
Xilution Beagily for data storage.
GraphQL enabled API running on a Hapi (NodeJS) server using the Apollo Server.

Prerequisites

Create a Xilution Account
1. Open https://prod.register.xilution.com to create a Xilution Prod account.
  - 📣 A valid credit card 💳 must be associated with your Xilution Account to use Xilution Products in Prod. Use the Prod environment Xilution Admin Portal to add a Credit Card to your Xilution Account.
2. Open https://test.register.xilution.com to create a Xilution Test account.
  - Xilution Test and Prod accounts are not synchronized.
  - Some Xilution products have usage and time to live restrictions in our Test environment. See product documentation for complete restriction details.
Install Docker Desktop: https://www.docker.com/products/docker-desktop
Install NVM: https://github.com/nvm-sh/nvm
Install Yarn: https://yarnpkg.com
Install jq: https://stedolan.github.io/jq/
Install cURL: https://curl.haxx.se/

General

To Install Dependencies

Run yarn install to download dependencies.

To Verify The Source Code

Run yarn verify.

Set Up

The following instructions are enabled via a large suite of scripts found in the scripts folder of this repo. You can see the changes made to your account via the scripts through our product portals. You'll authenticate to the portals with your Xilution Account username and password.

Portal	Prod	Test
Account	https://prod.portal.xilution.com/	https://test.portal.xilution.com/
Elephant	https://prod.portal.elephant.basics.xilution.com/	https://test.portal.elephant.basics.xilution.com/
Rhino	https://prod.portal.rhino.basics.xilution.com/	https://test.portal.rhino.basics.xilution.com/
Hippo	https://prod.portal.hippo.basics.xilution.com/	https://test.portal.hippo.basics.xilution.com/
Fox	https://prod.portal.fox.integration.xilution.com/	https://test.portal.fox.integration.xilution.com/

Environment Variables

Run touch .env to create a new environment variables file.
Run echo "XILUTION_ENVIRONMENT={environment}" >>.env to add your environment preference to the environment variables file (.env).
- {environment} is a Xilution environment. One of 'test' or 'prod'.

Account Organization Authentication

Run yarn xln:authentication:token-from-user-credentials.
- You will be prompted for your Xilution Account username and password.
- The access token saved to the environment variables file will expire in one hour.

Account Organization Product Activation

Note: Requires Account Organization Authentication

Run yarn xln:elephant:activate-for-account-organization.
Run yarn xln:hippo:activate-for-account-organization.
Run yarn xln:rhino:activate-for-account-organization.
Run yarn xln:fox:activate-for-account-organization.

Run yarn xln:{product-name}:show-activation-for-account-organization to see the status of an account organization's product activation.
- {product-name} is one of elephant, hippo, rhino or fox.
Run yarn xln:{product-name}:deactivate-for-account-organization to deactivate a product for an account organization.

Create a Xilution Sub-Organization

Note: Requires Account Organization Authentication

Run yarn xln:elephant:create-sub-organization.

📣 A valid credit card 💳 must be associated with your Xilution Sub-Organization to use Xilution Products in Prod. Use the Prod environment Xilution Elephant Portal to add a Credit Card to your Xilution Sub-Organization.
To see your Sub-Organizations, run yarn xln:elephant:show-organizations.
To delete a Sub-Organization, run yarn xln:elephant:delete-organization {sub-organization-id}
- {sub-organization-id} is a Sub-Organization id.

Sub-Organization Product Activation

Note: Requires Account Organization Authentication

Run yarn xln:zebra:activate-for-sub-organization.
Run yarn xln:beagily:activate-for-sub-organization.

Run yarn xln:{product-name}:show-activation-for-sub-organization to see the status of a Sub-Organization's product activation.
- {product-name} is one of zebra or beagily.
Run yarn xln:{product-name}:deactivate-for-sub-organization to deactivate a product for a Sub-Organization.

Add an API User to the Sub-Organization

Note: Requires Account Organization Authentication

Run yarn xln:rhino:sign-up-api-user {email} {username}.
- {email} is the new user's email address. Enter an email address that you have access to.
- {username} is the new user's username.
- A verification code will be emailed to the email address you entered when signing up the new user.
Run yarn xln:rhino:verify-user-email {username} {code} to verify the new user's email.
- {username} is the new user's username.
- {code} is the verification code the you received in your email inbox.

To see the Sub-Organization's users run, yarn xln:rhino:show-users.
To delete a Sub-Organization's user run, yarn xln:rhino:delete-user {user-id}.

Add an API Client to the Sub-Organization

Note: Requires Account Organization Authentication

Run yarn xln:hippo:create-api-client.

To see the Sub-Organization's clients run, yarn xln:hippo:show-clients.
To delete a Sub-Organization's client run, yarn xln:hippo:delete-client {client-id}.

Sub-Organization Authentication

Run yarn xln:zebra:token-from-api-client-credentials.

Prime Beagily with Some Data

Note: Requires Sub-Organization Authentication

Run yarn xln:beagily:create-pet-type.
Run yarn xln:beagily:create-pet {name} a few times, passing some different pet names.
- {name} is a pet's name.

Running Locally

Run export $(grep -v '^#' .env | xargs) to export environment variables into your current terminal session.
Run yarn start.
- You can make changes to the source code and nodemon will automatically restart the server when the changes are saved.
- Open http://localhost:3123/version in a browser to verify that the server is running.
- Open http://localhost:3123/graphql in a browser to see the Apollo Playground.
  - Requires Authentication. See Example GraphQL Queries and Mutations / Authentication below.
- Ctrl-c to stop.

Example GraphQL Queries and Mutations

You can use variants of the following queries to test your API in the Apollo Playground.

Authentication

For each of the following queries and mutations, you'll need to include the following header.

{
  "Authorization": "Bearer {xilution-api-access-token}"
}

Run yarn xln:zebra:token-from-api-client-credentials to regenerate an API access token.
Run cat .env | grep XILUTION_API_ACCESS_TOKEN to see the access token you just generated. You'll need this when you make requests to the API's graphql endpoint.
- Replace {xilution-api-access-token} in the JSON snippet above.

List Pets

Query

query Pets($sort: String, $query: String, $pageNumber: Int, $pageSize: Int) {
  pets(sort: $sort, query: $query, pageNumber: $pageNumber, pageSize: $pageSize) {
    data: content {
      id
      name
      createdAt
      owningUserId
    }
    total: totalElements
  }
}

Variables

{
	"pageNumber": {page-number},
	"pageSize": {page-size}
}

Get Pet

Query

query Pets($id: String!) {
  pet(id: $id) {
    id
    name
    createdAt
    owningUserId
  }
}

Variables

{
	"id": "{pet-id}"
}

Delete Pet

Mutation

mutation Pets($id: String!) {
  deletePet(id: $id) {
    id
  }
}

Variables

{
	"id": "{pet-id}"
}

Create Pet

Mutation

mutation Pets($newPet: NewPet!) {
  createPet(pet: $newPet) {
      id
      name
      createdAt
      owningUserId
  }
}

Variables

{
	"newPet": {
		"name": "{name}",
		"owningUserId": "{owning-user-id}"
	}
}

Update Pet

Mutation

mutation Pets($id: String! $updatedPet: UpdatedPet!) {
  updatePet(id: $id pet: $updatedPet) {
      id
      name
      createdAt
      owningUserId
  }
}

Variables

{
	"id": "{pet-id}",
	"updatedPet": {
		"name": "{name}"
	}
}

Host on Xilution Fox

Fox sources Docker images from Docker Hub. You grant Fox access to a Docker image hosted in Docker Hub in one of two ways.

Make the image public.
Add tbrunia as a collaborator.

Build the Docker image

This tags your docker image as xilution-graphql-backend-example.

Run yarn docker:build.

To run the Docker image locally

Run export $(grep -v '^#' .env | xargs) to export environment variables into your current terminal session.
Run yarn docker:start.
- Open http://localhost:3123/version to verify that the server is running.
- Because the Docker image was built in production mode, the Apollo Playground is not available.
- The GraphQL endpoint can by accessed at http://localhost:3123/graphql.

To stop the Docker image

Run yarn docker:stop.

Publish the Docker image to Docker Hub

You'll need a Docker Hub account to execute the following.

Run yarn docker:publish {docker_hub_account} to push the image to your Docker Hub account.

Create a Fox Instance

Note: Requires Account Organization Authentication

A Fox Instance contains data that instructs Fox on how to run your Docker image. You provision a Fox Instance to start your API. Likewise, you deprovision a Fox Instance to stop your API.

Run yarn xln:fox:create-instance {docker_hub_account}.

To see your instances, run yarn xln:fox:show-instances.
To delete a instance, run yarn xln:fox:delete-instance {fox-instance-id}.

Provision the Fox Instance

Note: Requires Account Organization Authentication

Run yarn xln:fox:provision-instance, to provision the Fox instance.
Run yarn xln:fox:show-instance-status, to see the status of your Fox instance.
- It can take up to 5 minutes to fully provision your Fox instance.
- Provisioning is complete when you see the following.
```
{
   "status": "CREATE_COMPLETE"
}
```
- Now you can access the GraphQL Example running on Fox.

Access The GraphQL Example Running on Fox

Run cat .env | grep XILUTION_FOX_INSTANCE_ID to see your Fox Instance ID.
Open https://{fox-instance-id}.{environment}.fox.integration.xilution.com/version in a browser to verify that the server is running.

The Apollo Playground is not available when running in Fox because the Docker image was built in production mode,

The GraphQL endpoint can by accessed at https://{fox-instance-id}.{environment}.fox.integration.xilution.com/graphql.
- Requires Authentication. See Example GraphQL Queries and Mutations / Authentication above.

Restart the Fox Instance

Note: Requires Account Organization Authentication and for the Fox instance to be provisioned.

You can make changes to your API, build and redeploy using the following commands.

Run yarn docker:build.
Run yarn docker:publish {docker_hub_account} to push the image to your Docker Hub account.
Run yarn xln:fox:restart-instance, to restart the instance in the Fox managed API hosting service.

We recommend adding a version endpoint to your API and use it to determine when a new version of your API has been deployed.

Deprovision the Fox Instance

Note: Requires Account Organization Authentication

Run yarn xln:fox:deprovision-instance, to deprovision the Fox instance.
Run yarn xln:fox:show-instance-status, to see the status of your Fox instance.
- It can take up to 5 minutes to fully deprovision your Fox instance.
- Deprovisioning is complete when you see the following.
```
{
   "status": "NOT_FOUND"
}
```

Delete the Fox Instance

Note: Requires Account Organization Authentication

Run yarn xln:fox:delete-instance {fox-instance-id}, to delete the Fox instance.

Name		Name	Last commit message	Last commit date
Latest commit History 94 Commits
.github/ISSUE_TEMPLATE		.github/ISSUE_TEMPLATE
docker		docker
scripts		scripts
src		src
.dockerignore		.dockerignore
.editorconfig		.editorconfig
.gitattributes		.gitattributes
.gitignore		.gitignore
.nvmrc		.nvmrc
.travis.yml		.travis.yml
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE		LICENSE
README.md		README.md
commitlint.config.js		commitlint.config.js
package.json		package.json
tsconfig.json		tsconfig.json
tslint.json		tslint.json
webpack.config.js		webpack.config.js
yarn.lock		yarn.lock

License

xilution/xilution-graphql-backend-example

Folders and files

Latest commit

History

Repository files navigation

xilution-graphql-backend-example

Time Requirement

Use Case

Xilution Product Hierarchy

Implemented Solution

Features

Prerequisites

General

To Install Dependencies

To Verify The Source Code

Set Up

Environment Variables

Account Organization Authentication

Account Organization Product Activation

Create a Xilution Sub-Organization

Sub-Organization Product Activation

Add an API User to the Sub-Organization

Add an API Client to the Sub-Organization

Sub-Organization Authentication

Prime Beagily with Some Data

Running Locally

Example GraphQL Queries and Mutations

Authentication

List Pets

Get Pet

Delete Pet

Create Pet

Update Pet

Host on Xilution Fox

Build the Docker image

To run the Docker image locally

To stop the Docker image

Publish the Docker image to Docker Hub

Create a Fox Instance

Provision the Fox Instance

Access The GraphQL Example Running on Fox

Restart the Fox Instance

Deprovision the Fox Instance

Delete the Fox Instance

About

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

Packages 0

Contributors 2

Languages

Packages