Book Image

Building RESTful Web services with Go

By : Naren Yellavula
Book Image

Building RESTful Web services with Go

By: Naren Yellavula

Overview of this book

REST is an architectural style that tackles the challenges of building scalable web services and in today's connected world, APIs have taken a central role on the web. APIs provide the fabric through which systems interact, and REST has become synonymous with APIs. The depth, breadth, and ease of use of Go, makes it a breeze for developers to work with it to build robust Web APIs. This book takes you through the design of RESTful web services and leverages a framework like Gin to implement these services. The book starts with a brief introduction to REST API development and how it transformed the modern web. You will learn how to handle routing and authentication of web services along with working with middleware for internal service. The book explains how to use Go frameworks to build RESTful web services and work with MongoDB to create REST API. You will learn how to integrate Postgres SQL and JSON with a Go web service and build a client library in Go for consuming REST API. You will learn how to scale APIs using the microservice architecture and deploy the REST APIs using Nginx as a proxy server. Finally you will learn how to metricize a REST API using an API Gateway. By the end of the book you will be proficient in building RESTful APIs in Go.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Using Redis for caching the API data


Redis is an in-memory database that can store key/value pairs. It best suits the caching use cases where we need to store information temporarily but for huge traffic. For example, sites such as BBC and The Guardian show the latest articles on the dashboard. Their traffic is so high, if documents (articles) are fetched from the database, they need to maintain a huge cluster of databases all the time. Since the given set of articles does not change (at least for hours), the BBC can maintain a cache which saves the articles. When the first customer visits the page, a copy is pulled from the DB, sent to the browser, and placed in the Redis cache. The next time a customer appears, the BBC application server reads content from Redis instead of going to the DB. Since Redis runs in primary memory, latency is reduced. The customer sees his page loaded in a flash. The benchmarks on the web can tell more about how efficiently a site can optimize its contents.

What...