Book Image

Full-Stack Web Development with Go

By : Nanik Tolaram, Nick Glynn
Book Image

Full-Stack Web Development with Go

By: Nanik Tolaram, Nick Glynn

Overview of this book

Go is a modern programming language with capabilities to enable high-performance app development. With its growing web framework ecosystem, Go is a preferred choice for building complete web apps. This practical guide will enable you to take your Go skills to the next level building full stack apps. This book walks you through creating and developing a complete modern web service from auth, middleware, server-side rendering, databases, and modern frontend frameworks and Go-powered APIs. You’ll start by structuring the app and important aspects such as networking, before integrating all the different parts together to build a complete web product. Next, you’ll learn how to build and ship a complete product by starting with the fundamental building blocks of creating a Go backend. You’ll apply best practices for cookies, APIs, and security, and level up your skills with the fastest growing frontend framework, Vue. Once your full stack application is ready, you’ll understand how to push the app to production and be prepared to serve customers and share it with the world. By the end of this book, you’ll have learned how to build and ship secure, scalable, and complete products and how to combine Golang with existing products using best practices.
Table of Contents (21 chapters)
1
Part 1: Building a Golang Backend
5
Part 2:Serving Web Content
9
Part 3:Single-Page Apps with Vue and Go
14
Part 4:Release and Deployment

Use cases for using feature flags

Feature flags are not limited to flags that can be configured to turn on/off features inside applications; there are many more features and capabilities. In this section, we will look at the features provided in a full-blown feature flag server:

  • Segment targeting – Imagine you are building a feature that you want to test on a group of users in your application. For example, you may want a certain group of users that are based in the USA to use the checkout feature based on PayPal.
  • Risk mitigation – Building product features does not guarantee that a feature will bring in more users. New features can be released and, with time and more analysis, if it is found that the feature is providing a bad user experience, it will be turned off as part of the risk mitigation process.
  • Gathering feedback before launch – Using a targeted rollout for a certain group of users, it is possible to get feedback as early as possible...