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)

Deployment options

We have looked at various strategies for scaling our application, different types of databases, how to structure our code, and finally how to use the mediator pattern to make the transition from monolith to microservices. However, we haven't discussed where we would be deploying said web application and databases. Let's take a brief look at the deployment landscape.

Till the early 2000s, most servers were deployed on hardware owned by the companies writing the software. There would be dedicated infrastructure and a team to deal with this critical part of software engineering. This was mostly the subject of data centers.

However, in the 2000s, companies began to realize that data centers could be abstracted away because most of the developers weren't interested in handling these problems. This allowed for cheaper and faster development and deployment...