Go Time: Golang, Software Engineering

Event-driven systems

May 13, 2021
Ask episode
Chapters
Transcript
Episode notes
1
Introduction
00:00 • 3min
2
How Are You Doing With Event Powered Systems?
02:57 • 2min
3
What's Your Experience With Event Powered Microservices?
05:13 • 2min
4
What Is an Event Driven Architecture?
07:03 • 2min
5
Message Brokers in an Event Driven System
08:48 • 2min
6
The Benefits of Event Driven Architectures
10:20 • 5min
7
What Can a User Tolerate Before They Close the Page or Put Your App Down?
15:14 • 2min
8
What Is an Event Bus?
16:57 • 4min
9
The Snake Oil of Perpetual Motion Machines
21:17 • 3min
10
What Is the Difference Between Event-Driven and Event-Driving?
24:42 • 2min
11
Event Sourcing - The Biggest Positive of Replaying Events
26:18 • 3min
12
Are You Using Event Sourcing or Event Driven?
29:00 • 3min
13
How to Write Protobuf Schemas?
31:52 • 5min
14
Using Go in an Event Powered System?
36:58 • 5min
15
Using Event Driven for High Throughput Messages?
41:34 • 1min
16
Is SCD a Good Use Case for a Cold Caching Layer?
42:50 • 5min
17
Kubernetes Deployment?
47:52 • 2min
18
Continuous Deployment - Is Master What Should Be Running in Production?
49:47 • 3min
19
The Overuse of ER, E-R-R as an Error Variable Makes Code Harder to Read
52:40 • 2min
20
I've Never Found a Use for the Naked Braces
54:52 • 2min
21
The Problem With Errors in Go
56:25 • 2min
22
Is There a Difference Between Context and Error?
58:45 • 2min
23
Type Switches on the Errors
01:00:26 • 4min
24
Do You Have to Handle the Errors?
01:04:31 • 3min
25
How to Resolve Security Errors
01:07:19 • 2min
26
Go Time Podcast Review
01:08:58 • 2min