Book Image

Hands-On RESTful Web Services with Go - Second Edition

By : Naren Yellavula
Book Image

Hands-On RESTful Web Services with Go - Second Edition

By: Naren Yellavula

Overview of this book

Building RESTful web services can be tough as there are countless standards and ways to develop API. In modern architectures such as microservices, RESTful APIs are common in communication, making idiomatic and scalable API development crucial. This book covers basic through to advanced API development concepts and supporting tools. You’ll start with an introduction to REST API development before moving on to building the essential blocks for working with Go. You’ll explore routers, middleware, and available open source web development solutions in Go to create robust APIs, and understand the application and database layers to build RESTful web services. You’ll learn various data formats like protocol buffers and JSON, and understand how to serve them over HTTP and gRPC. After covering advanced topics such as asynchronous API design and GraphQL for building scalable web services, you’ll discover how microservices can benefit from REST. You’ll also explore packaging artifacts in the form of containers and understand how to set up an ideal deployment ecosystem for web services. Finally, you’ll cover the provisioning of infrastructure using infrastructure as code (IaC) and secure your REST API. By the end of the book, you’ll have intermediate knowledge of web service development and be able to apply the skills you’ve learned in a practical way.
Table of Contents (16 chapters)

Exercise

Can you design the following requirements?

Develop a /healthcheck API with token authentication. Its main responsibilities should be as follows:

  • Authenticate the client and return a JWT string
  • Authorize client API requests by validating the JWT

You should use the knowledge you gained about the jwt-go package from the previous section. You have to build two endpoints, as follows:

  • /getToken
  • /healthcheck

The first endpoint should successfully log in a client and return a JWT token. The client should then use the second endpoint with the token to receive a successful response.

Post-development, the final API testing scenario should look something similar to this:

  1. If you make a GET request to the /healthcheck API without any token, you should receive an Access Denied message, as shown here:
Access Denied; Please check the access token
  1. You should be able to authenticate...