Book Image

Hands-On Full Stack Development with Go

By : Mina Andrawos
Book Image

Hands-On Full Stack Development with Go

By: Mina Andrawos

Overview of this book

The Go programming language has been rapidly adopted by developers for building web applications. With its impressive performance and ease of development, Go enjoys the support of a wide variety of open source frameworks, for building scalable and high-performant web services and apps. Hands-On Full Stack Development with Go is a comprehensive guide that covers all aspects of full stack development with Go. This clearly written, example-rich book begins with a practical exposure to Go development and moves on to build a frontend with the popular React framework. From there, you will build RESTful web APIs utilizing the Gin framework. After that, we will dive deeper into important software backend concepts, such as connecting to the database via an ORM, designing routes for your services, securing your services, and even charging credit cards via the popular Stripe API. We will also cover how to test, and benchmark your applications efficiently in a production environment. In the concluding chapters, we will cover isomorphic developments in pure Go by learning about GopherJS. As you progress through the book, you'll gradually build a musical instrument online store application from scratch. By the end of the book, you will be confident in taking on full stack web applications in Go.
Table of Contents (15 chapters)
Free Chapter
1
Section 1: The Go Language
5
Section 2: The Frontend
8
Section 3: Web APIs and Middleware in Go

Questions

  1. What is concurrency?
  2. What is a thread?
  3. How is the concept of concurrency different from parallel threading?
  4. What is a goroutine?
  5. What does share memory by communicating mean?
  6. What is a Go channel?
  7. What is the difference between a regular Go channel and a buffered Go channel?
  8. When should you use a select statement?
  9. What is the difference between sync.Mutex and sync.RWMutex?
  10. When should you use wait groups?