I am also interested in creating and communicating with GraphQL services using PRPC.

Ideally, a future version of PRPC will have an ootb class for Connect-GraphQL.

Until then, has anyone tried building GraphQL connectors on top of HTTP connectors?

Hi,

Please check below post. It may help you.

https://collaborate.pega.com/question/pega-support-graphql

graphQL is basically a REST with typed parameters.

If you need to access your company internal/or any other graphQL end point, just pre cook  your grapql Queries withe the exact paramaters that you would do if it was a micro service.

for example: let say you have this schema : from apollo.org

directive @cacheControl(
  maxAge: Int
  scope: CacheControlScope
) on FIELD_DEFINITION | OBJECT | INTERFACE
type Book {
  title: String
  author: String
}

enum CacheControlScope {
  PUBLIC
  PRIVATE
}

type Query {
  books: [Book]
}

scalar Upload

then if you want only the list of books. your REST post data would be like this.

{
  books {
    title
      }
}

in other words, you can make your GraphQL end point compatible with the legacy REST. and serve REST and graphQL clients at the same time.

graphQL is basically a REST with typed parameters.

If you need to access your company internal/or any other graphQL end point, just pre cook  your grapql Queries withe the exact paramaters that you would do if it was a micro service.

for example: let say you have this schema : from apollo.org

directive @cacheControl(
  maxAge: Int
  scope: CacheControlScope
) on FIELD_DEFINITION | OBJECT | INTERFACE
type Book {
  title: String
  author: String
}

enum CacheControlScope {
  PUBLIC
  PRIVATE
}

type Query {
  books: [Book]
}

scalar Upload

then if you want only the list of books. your REST post data would be like this.

"query={
  books {
    title
      }
}"

in other words, you can make your GraphQL end point compatible with the legacy REST. and serve REST and graphQL clients at the same time.