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

What are microservices?


What are microservices? This is the question the enterprise world is asking the computing world. Because of the bigger teams, the companies are ready to embrace microservices for breaking down tasks. Microservice architecture replaces the traditional monolith with granular services that talk to each other with some kind of agreement.

Microservices bring the following benefits to the plate:

  • If the team is big, people can work on chunks of applications
  • Adaptability is easy for the new developers
  • Adopting best practices, such as Continuous Integration (CI) and Continuous Delivery (CD)
  • Easily replaceable software with loosely coupled architecture

In a monolith application (traditional application), a single huge server serves the incoming requests by multiplexing the computing power. It is good because we have everything, such as an application server, database, and other things, in a single place. It also has disadvantages. When a piece of software breaks, everything breaks...