Scaling Go Applications: Difference between revisions

From bibbleWiki
Jump to navigation Jump to search
Line 15: Line 15:
*Centralized Logging
*Centralized Logging
AGAIN this is an approach and of course you can use third-party cloud solutions. This one will be confined to Docker and GO.
AGAIN this is an approach and of course you can use third-party cloud solutions. This one will be confined to Docker and GO.
==Initial Optimizations==
==Creating a Load Balancer==
==Caching==
==Centralized Logging==

Revision as of 11:53, 28 January 2021

Introduction

Resources

When we look at scaling we must consider the following resources.

  • Network Bandwidth
  • Processing Power
  • Available Memory
  • Data Storage

For this page we will be looking a the challenges around breaking an application in to several servers and following an architecture such as below This not meant to be THE solution but a walkthrough on some of the challenges to scale. This will be split into

  • Initial Optimizations
  • Creating a Load Balancer
  • Caching
  • Centralized Logging

AGAIN this is an approach and of course you can use third-party cloud solutions. This one will be confined to Docker and GO.

Initial Optimizations

Creating a Load Balancer

Caching

Centralized Logging