Book Overview & Buying
Table Of Contents

Distributed Computing with Go

By : V.N. Nikhil Anurag

3.6 (5)

Buy this Book

Distributed Computing with Go

3.6 (5)

By: V.N. Nikhil Anurag

Buy this Book

Overview of this book

Distributed Computing with Go gives developers with a good idea how basic Go development works the tools to fulfill the true potential of Golang development in a world of concurrent web and cloud applications. Nikhil starts out by setting up a professional Go development environment. Then you’ll learn the basic concepts and practices of Golang concurrent and parallel development. You’ll find out in the new few chapters how to balance resources and data with REST and standard web approaches while keeping concurrency in mind. Most Go applications these days will run in a data center or on the cloud, which is a condition upon which the next chapter depends. There, you’ll expand your skills considerably by writing a distributed document indexing system during the next two chapters. This system has to balance a large corpus of documents with considerable analytical demands. Another use case is the way in which a web application written in Go can be consciously redesigned to take distributed features into account. The chapter is rather interesting for Go developers who have to migrate existing Go applications to computationally and memory-intensive environments. The final chapter relates to the rather onerous task of testing parallel and distributed applications, something that is not usually taught in standard computer science curricula.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Developer Environment for Go

GOROOT

GOPATH

Package management

Structuring a project

Working with book's code

Containers

Testing in Go

Summary

Understanding Goroutines

Concurrency and parallelism

Go's runtime scheduler

Gotchas when using goroutines

Summary

Channels and Messages

Controlling parallelism

Channels and data communication

Types of channels

Closing channels

Multiplexing channels

Summary

The RESTful Web

HTTP and sessions

The REST protocol

Fundamentals of a REST server

How to make REST calls

Summary

Introducing Goophr

What is Goophr?

Design overview

OpenAPI specification

Project structure

Summary

Goophr Concierge

Revisiting the API definition

Document feeder – the REST API endpoint

Query handler – the REST API endpoint

Conventions

Logical flow diagrams

The Concierge source code

Summary

Goophr Librarian

The standard indexing model

The inverted indexing model

Ranking

Revisiting the API definition

The document indexer – the REST API endpoint

The query resolver – the REST API endpoint

Code conventions

Librarian source code

Testing Librarian

Summary

Deploying Goophr

Updating Goophr Concierge

Orchestrating with docker-compose

The Goophr source code

Running Goophr with docker-compose

Searching for keywords with Goophr

Authorization on a web server

Summary

Foundations of Web Scale Architecture

Scaling a web application

Monolith versus microservices

Deployment options

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think

Project structure

As per the previous diagram, we have designed our application to consist of one instance of Goophr Concierge and three instances of Goophr Librarian. In order to keep our code manageable, we will split the source code into two main entities and a docker-compose file at the root level:

Concierge
Librarian
docker-compose.yaml

In Chapter 1, Developer Environment for Go, we discussed how to create and run docker images. The docker run ... works great for single images, but it might get complicated when we want to create a network of docker images that interact with one another. In order to keep the setup simple, we will make use of docker-compose (https://docs.docker.com/compose/overview/). In a nutshell, docker-compose requires a YAML (Yet Another Markup Language) file with specifics such as what to name the running docker images, what ports to run them on, and...