There are a few families of status codes. Each family globally explains an operation status. Each member of that family may have a deeper meeting. So a REST API should strictly tell the client what exactly happened after the operation. There are 60+ status codes available. But for REST, we concentrate on a few families of codes.
- Preface
- Getting Started with REST API Development
- Handling Routing for Our REST Services
- Working with Middleware and RPC
- Simplifying RESTful Services with Popular Go Frameworks
- Working with MongoDB and Go to Create REST APIs
- Working with Protocol Buffers and GRPC
- Working with PostgreSQL, JSON, and Go
- Building a REST API Client in Go and Unit Testing
- Getting the code
- Plan for building a REST API client
- Basics for writing a command-line tool in Go
- grequests – a REST API package for Go
- Getting comfortable with the GitHub REST API
- Creating a CLI tool as an API client for the GitHub REST API
- Using Redis for caching the API data
- Creating a unit testing tool for our URL shortening service
- Summary
- Scaling Our REST API Using Microservices
- Deploying Our REST services
- Using an API Gateway to Monitor and Metricize REST API
- Handling Authentication for Our REST Services
Types of status codes
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.