-
Notifications
You must be signed in to change notification settings - Fork 2
Home
This course teaches you how to build production-level services in Go, leveraging the power of a Domain Driven, Data Oriented Archiecture deployed in Encore. 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 and Images to Install
We begin to build the service with a focus on the ability to deploy the service in Kuberenetes.
- 2.1: Project Layers, Policies, and Guidelines
- 2.2: Prepare Project
- 2.3: Build Encore Service with Logging
- 2.4: Add Test API Handler
- 2.5: Deploy to Encore Cloud
We finish the initial startup and shutdown of the service.
- 3.1: Configuration
- 3.2: Debugging / Metrics
We add middleware functions for business-level logic that needs to be injected into the processing of requests.
- 4.1: Panic Handling
- 4.2: Metrics
We gain an understanding of how JWT's work and their shortcomings. We also learn about OPA and how we will use it to perform the actual authentication and authorization.
- 5.1: Understanding JWT
- 5.2: Private/Public Key Generation
- 5.3: Token Generation
- 5.4: Token Signature Validation with OPA
We create add a secret for the private key.
- 6.1: Secret Support
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.
- 7.1: Auth Package
- 7.2: Auth Unit Test
- 7.3: Add Middleware
- 7.4: Auth Service
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.
- 8.1: Architecture Review
- 8.2: Data Flow Trust vs Non-Trust
We add a Postgres database to our Encore 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.
- 9.1: Encore Support for Postgres
- 9.2: Create Database Package
- 9.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 Encore to run the migration and seeding on POD startup.
- 10.1: Maintaining Database Schemas and Seeds
- 10.2: Admin Tooling and Init Containers to Automate Migrations
We implement the User domain inside the App, Business, and Storage layers.
- 11.1: User Business Domain Support
- 11.2: User Storage Domain Support
- 11.3: User App Domain Support
- 11.4: User API Domain Support
We add docker and unit testing support for writing tests against a real database and write the actual user package tests.
- 12.1: Starting and Stopping Containers
- 12.2: Database Testing Support
- 12.3: Unit and API Testing Support
- 12.4: Write User Business Test
- 12.5: Write User API Tests
We talk about how the delegate and transaction systems work.
- 13.1: Delegate System
- 13.2: Transaction System
Review service project and get it running
- 14.1: Check For Dependcy Upgrades, Rebuild, Run