Server Side GraphQL

GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.

  • Nov 18
    Online
    1 day
    08:00 - 14:00 UTC
    Craig West
    150 USD

We create several GraphQL Servers, each time implementing new features.

## PART-01

Exploration of GraphQL concepts to make CRUD GraphQL Server with HTML client requests. This can also be used as a wrapper around existing REST APIs enabling a gradual transition to GraphQL.

## PART-02

With another GraphQL Server, we add in some new features leading to COURSE-03. We connect to other APIs to enable our GraphQL Server to act as a central API point.

## PART-03

We refactor the previous Server and start to use Schema Merging and code refactoring to enable greater modularity to our code.

## PART-04

We move on to more advanced topics:

- More work on the resolver chain.
- Unions, Interfaces, Enums and Custom Scalar types.
- Error handling and formatting.
- Authentication and Authorization techniques.
- Subscriptions.
- Custom directives.
- Caching.
- Security, DDOS.

We use JavaScript minimally and the GraphQL concepts taught are transferrable to any code base.

Craig West
Offline first!

Craig is freelance trainer and architect tbased in Brighton, UK and attends many local Web Development meetings. With a previous career in business and accounting, as well as having run his own non-IT business, Craig can speak both technical and business. He believes that technology serves the user, not the other way around, so the user experience is paramount.

He has given talks and workshops at events and is interested in Web Components, Progressive Web Apps, React, WordPress and JavaScript with a strong interest in pages that are ‘instant’ and/or offline capable.

    NDC Conferences uses cookies to see how you use our website. We also have embeds from YouTube and Vimeo. How do you feel about that?