Software Architecture

2018

Videos

1 — Reactive DDD—When Concurrent Waxes Fluent
2 — From Winning the Microservice War to Keeping the Peace
3 — An Engineer's Guide to a Good Night's Sleep
4 — Microservices for Growth at comparethemarket.com
5 — Evolution of Financial Exchange Architectures
6 — Introducing and Scaling a GraphQL BFF
7 — Why Distributed Systems Are Hard
8 — Streaming a Million Likes/Second: Real-Time Interactions on Live Video
9 — Moving beyond Request-Reply: How Smart APIs Are Different
10 — To Microservices and Back Again
11 — Cloudstate—towards Stateful Serverless
12 — From Batch to Streaming to Both
13 — Modern Banking in 1500 Microservices
14 — Kafka: A Modern Distributed System
15 — Monolith Decomposition Patterns
16 — Rampant Pragmatism: Growth and Change at Starling Bank
17 — Panel: Microservices - Are They Still Worth It?
18 — A Brief History of the Future of the API
19 — Tesla Virtual Power Plant
20 — Service Mesh Ultimate Guide: Managing Service-to-Service Communications in the Era of Microservices
21 — Build Your Own WebAssembly Compiler
22 — Parsing JSON Really Quickly: Lessons Learned
23 — Beyond Microservices: Streams, State and Scalability
24 — Interaction Protocols in Software: It's All about Good Manners
25 — Continuous Profiling in Production: What, Why and How
26 — Reactive Systems Architecture
27 — Performance: What's Next?
28 — Crisis to Calm: Story of Data Validation @ Netflix
29 — Mature Microservices and How to Operate Them
30 — Restoring Confidence in Microservices: Tracing That's More Than Traces
31 — Connecting, Managing, Observing, and Securing Services
32 — Patterns of Streaming Applications
33 — Paying Technical Debt at Scale - Migrations @Stripe
34 — CRDTs in Production
35 — The Great Migration: from Monolith to Service-Oriented
36 — What We Got Wrong: Lessons from the Birth of Microservices
37 — Actors or Not: Async Event Architectures
38 — How to Build Observable Distributed Systems
39 — The Present and Future of Serverless Observability
40 — Applied Performance Theory
41 — Insecure Transit - Microservice Security
42 — How Events Are Reshaping Modern Systems
43 — Microservices Lessons Learned from a Startup
44 — Avoiding Alerts Overload from Microservices
45 — Chaos Architecture
46 — Scaling Facebook Live Videos to a Billion Users
47 — Mastering Chaos - A Netflix Guide to Microservices
48 — Building a Bank with Go
49 — Spotify's Reliable Event Delivery System
50 — Applying Failure Testing Research @Netflix
51 — From Concurrent to Parallel
52 — What Comes after Microservices?
53 — In-Memory Caching: Curb Tail Latency with Pelikan
54 — From Microliths to Microsystems
55 — Distributed Systems Theory for Practical Engineers
56 — How Slack Works
57 — Scaling Slack
58 — Architecting a Modern Financial Institution
59 — Service-Oriented Development
60 — Data Consistency in Microservice Using Sagas
61 — Istio - Weaving the Service Mesh
62 — The Evolution of Reddit.com's Architecture
63 — The Anatomy of a Distributed System
64 — The Future of Artificial Intelligence
65 — Testing in Production - Quality Software Faster
66 — Scaling Patterns for Netflix's Edge
67 — Beyond the Distributed Monolith: Rearchitecting the Big Data Platform
68 — Designing Secure Architectures the Modern Way, Regardless of Stack
69 — Reconciling Performance and Security in High Load Environments
70 — Lessons from DAZN: Scaling Your Project with Micro-Frontends
71 — Infinite Parallel Universes: State at the Edge
72 — The Correct Number of Microservices for a System Is 489 (Panel)
73 — Complex Event Flows in Distributed Systems
74 — CRDTs and the Quest for Distributed Consistency
75 — Building Tech at Presidential Scale
76 — Data Mesh in the Real World: Lessons Learnt from the Financial Markets
77 — Co-Designing Raft + Thread-per-Core Execution Model for the Kafka-API
78 — Architecting Software for Leverage
79 — Resources & Transactions: a Fundamental Duality in Observability
80 — Building and Scaling a Control Plane for 1000s of Kafka Clusters
81 — Panel: What Have We Learned over the Last Decade of Microservices?
82 — Complex Systems: Microservices and Humans
83 — Unwinding a Decade of Assumptions - Architecting New Experiences
84 — Panel: Event Driven Architectures of Scale
85 — User Adaptive Security
86 — Pitfalls and Patterns in Microservice Dependency Management
87 — Minimizing Design Time Coupling in a Microservice Architecture
88 — Essential Complexity in Systems Architecture
89 — Architecting for Focus, Flow, and Joy: beyond the Unicorn Project
90 — Pragmatic Performance - Tales from the Trenches
91 — The World Is on Fire and so Is Your Website
92 — User Simulation for Rapid Outage Mitigation
93 — Change Data Capture for Distributed Databases @Netflix
94 — Rebuilding Twitter’s Public API
95 — Solving Mysteries Faster with Observability
96 — How to Tame Your Service APIs: Evolving Airbnb’s Architecture
97 — From Monolith to Microservices
98 — It’s Not Your Machine, It’s Your Code
99 — The Medieval Census Problem
100 — Building Latency Sensitive User Facing Analytics via Apache Pinot
101 — How Netflix Scales Its API with GraphQL Federation
102 — Netflix Play API - An Evolutionary Architecture
103 — Designing Services for Resilience: Netflix Lessons
104 — Microservices: Patterns and Practices Panel
105 — Why We Chose Erlang over Java, Scala, Go, C
106 — Real-Time & Personalized Notifications @Twitter
107 — DDD and Microservices: At Last, Some Boundaries!
108 — Cloud-Native and Scalable Kafka Architecture
109 — Chaos Engineering: Why the World Needs More Resilient Systems