Book Image

Distributed Computing with Go

By : V.N. Nikhil Anurag
Book Image

Distributed Computing with Go

By: V.N. Nikhil Anurag

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.
Table of Contents (11 chapters)

The Goophr source code

In the previous two chapters, Chapter 6, Goophr Concierge and Chapter 7, Goophr Librarian, we discussed the code for Concierge and Librarian respectively. In order to run the complete Goophr application using docker-compose, we will need to merge the codebases of both Librarian and Concierge into a single codebase. The codebase will also include docker-compose.yaml and code for the file server.

In this chapter, we will not list the code for all the files in Librarian and Concierge but only the files with changes. Let's start by looking at the structure of the complete project:

$ tree -a
ε2;── goophr
    ├── concierge
    │   ├── api
    │   │   ├── feeder.go
    │   │   ├── feeder_test.go
    │   │...