Book Image

Full Stack Development with Angular and GraphQL

By : Ahmed Bouchefra
Book Image

Full Stack Development with Angular and GraphQL

By: Ahmed Bouchefra

Overview of this book

GraphQL is an alternative to traditional REST technology for querying Web APIs. Together with Angular and TypeScript, it provides a tech stack option for building future-proof web applications that are robust and maintainable at any scale. This book leverages the potential of cutting-edge technologies like GraphQL and Apollo and helps Angular developers add it to their stack. Starting with introducing full-stack development, you will learn to create a monorepo project with Lerna and NPM Workspaces. You will then learn to configure Node.js-based backend using GraphQL, Express, and Apollo Server. The book will demonstrate how to build professional-looking UIs with Angular Material. It will then show you how to create Web APIs for your frontend with GraphQL. All this in a step-by-step manner. The book covers advanced topics such as local state management, reactive variables, and generating TypeScript types using the GraphQL scheme to develop a scalable codebase. By the end of this book, you'll have the skills you need to be able to build your full-stack application.
Table of Contents (16 chapters)
1
Part 1: Setting Up the Development Environment, GraphQL Server, and Database
7
Part 2: Building the Angular Frontend with Realtime Support
13
Part 3: Adding Realtime Support

What's JWT?

JWT stands for JSON Web Token, and it's an open standard (RFC 7519) that offers a concise and self-contained mechanism for securely encoding and transmitting information between computers as JSON objects.

When developing GraphQL APIs, you'll almost always need to secure specific endpoints from public access and need users to be authenticated first and authorized (allowed) to use the endpoint(s).

You can achieve that using JWTs. This is how authentication with JWTs works:

  1. When users register or sign in, we build a JWT token that includes the user's identity on the server and send it to the client.
  2. We need to transmit the received token back to the server with every request on the client side so that the server can verify the client's identity and determine whether they are permitted to visit the endpoint.

In contemporary web apps, where we have a JavaScript client app that has to interface with an API to query and save data...