-
Notifications
You must be signed in to change notification settings - Fork 652
Course Outline
This course teaches you how to build production-level services in Go, leveraging the power of a Domain Driven, Data Oriented Archiecture deployed in Kubernetes. From the beginning of the course, you will pair-program with your instructor Bill Kennedy as he walks you through the design philosophies, architectural decisions, and best practices as they apply to engineering a production-ready Go service.
With each new feature that is added to the service, you will learn how to deploy and manage the Kubernetes environment used to run the service. Throughout the class, the code being worked on is pushed to a repository for personal access and review.
For further class information, please see the class schedule or review the self-study options
This class tries to teach to these core design philosophies, review practices, and culture.
There are three core design philosophies that drive every guideline:
- Don’t make things easy to do, make things easy to understand.
- Every encapsulation must define a new and precise semantic.
- Engineer with clear and obvious layers of concern and purpose.
There are three core reviews that must be performed with each change:
- Can this change be maintained, managed, and debugged by the team?
- Is this change the minimal code needed right now to solve the problem?
- Does this change violate any style or project guidelines?
There are three core aspects of a team’s culture that should be cultivated:
- Uncertainty is not a license to guess, but a directive to stop and learn more.
- Don’t focus on reuse, focus on constant review and refactoring.
- Be open to discussion and pivot as new things are learned and discovered.
Introduction to the class and all the engineering that you will learn.
- 1.1: Design Philosophy, Guidelines, What to Expect
- 1.2: Tooling to Install
- 1.3: Images to Install
A walkthrough of how the module ecosystem works. We talk about the engineering decisions you need to make as they relate to modules.
- 2.1: Adding Dependencies
- 2.2: Module Mirrors
- 2.3: Checksum Database
- 2.4: Vendoring
- 2.5: MVS Algorithm
- 2.6: Upgrading Dependencies
We begin to build the service with a focus on the ability to deploy the service in Kuberenetes.
- 3.1: Project Layers, Policies, and Guidelines
- 3.2: Prepare Project
- 3.3: Logging
We introduce Kubernetes and get a K8s environment up and running. At this point, everything we do runs in the K8s environment.
- 4.1: Clusters, Nodes and Pods
- 4.2: Start the Kubernetes Cluster
- 4.3: Create/Build Dockerfile for the Service
- 4.4: Create/Apply K8s Deployment for the Service
We introduce applying Quotas to the deployment and discuss the problems that can result.
- 5.1: Understanding CPU Quotas
- 5.2: Understanding the Go Scheduler
- 5.3: Adjust GOMAXPROCS to maximize performance
We finish the initial startup and shutdown of the service.
- 6.1: Configuration
- 6.2: Debugging / Metrics
- 6.3: Shutdown Signaling and Load Shedding
We build out our own router by extending an existing one. This gives us a framework for injecting business logic into the processing of requests. It also allows for more consistency in the handling of requests.
- 7.1: Basic Structure of an HTTP Router
- 7.2: Liveness and Readiness Handlers
- 7.3: Customize the Router
- 7.4: Middleware Support
- 7.5: Sending Responses
We add middleware functions for business-level logic that needs to be injected into the processing of requests.
- 8.1: Logging
- 8.2: Error Handling
- 8.2.1: Understanding what Error Handling Means
- 8.2.2: Declaring Custom Error Types
- 8.2.3: Consistent Handling and Response
- 8.3: Panic Handling
- 8.4: Metrics
We gain an understanding of how JWT's work and their shortcomings.
- 9.1: Understanding JWT
- 9.2: Private/Public Key Generation
- 9.3: Token Generation
- 9.4: Token Signature Validation
We create a simple key store for the project to store and retrieve the private key.
- 10.1: Key Store Package
We integrate authentication and authorization support into the project by developing a packages to generate and validate tokens. Then we integrate the packages into the application and test things are working.
- 11.1: Auth Package
- 11.2: Open Policy Agent
- 11.3: Auth Unit Test
- 11.4: Add Middleware
We talk about the need for liveness and readiness probes and how to integrate them into the solution.
- 12.1: Check Group Routes
- 12.2: K8s Base Sales Changes
We talk about the data driven data oriented architecture that is implemented in the project. We discuss the design philosophy, guidelines, and semantics of how the three layers of App, Business, and Storage work together.
- 13.1: Architecture Review
- 13.2: Data Flow Trust vs Non-Trust
We add a Postgres database to our K8s environment. Then we write a small database package that provides support for using the SQLx package more effectively. Finally, integrate the database package on application startup.
- 14.1: Kubernetes Support for Postgres
- 14.2: Create Database Package
- 14.3: Update Readiness Handler to Perform DB Checks
We define our schema and provide support for migration schema changes over time. We also provide support for seeding the database. Finally, we add support in Kubernetes to run the migration and seeding on POD startup.
- 15.1: Maintaining Database Schemas
- 15.2: Seeding Data
- 15.3: Add Init Containers to Automate Migrations
We implement the Create domain inside the App, Business, and Storage layers.
- 16.1: User Business Layer Support
- 16.2: User Storage Layer Support
- 16.3: User App Layer Support
- 16.4: User Database Migration Support
- 16.5: Run Project To Test
We add docker and unit testing support for writing unit tests against a real database and write the actual user package tests.
- 17.1: Starting and Stopping Containers
- 17.2: Starting and Stopping a Test
- 17.3: Write User Unit Test
We talk about how to add transactions to the system that will allow for cross domain transactions.
- 18.1: Design Philosophies, Policies, and Guidelines
- 18.2: Transaction Interfaces and Support
- 18.3: Transaction Middleware
- 18.4: Storage, Business, and Application Integration
We add tracing to the project by integrating Open Telemetry and Zipkin.
- 19.1: Integrate OTEL Web Handler into the Framework
- 19.2: Integrate OTEL into Service Startup
- 19.3: Add Tracing Calls Inside Functions to Trace
- 19.4: Kubernetes Support for Grafana, Prometheus, Tempo, Loki, and Promtail
Review service project and get it running
- 20.1: Check For Dependcy Upgrades
- 20.2: Rebuild and Run the Project
Contact Bill Kennedy at [email protected] if you are having issues getting the project running.