garbagedestroyer

Videos

Software benchmarks, systems deep-dives, and technical commentary. Subscribe on YouTube

The hidden cost of using BFF #SoftwareDesign #Engineering
SHORT
0:35
The hidden cost of using BFF #SoftwareDesign #Engineering

BFF was designed for 2015 when API gateways couldn't shape payloads. In 2026, gateways handle this natively โ€” BFF adds unnecessary operational overhead. ## Key Points - Gateways now handle payload shaping natively - 3 clients = 3 BFFs = 3 on-call rotations - BFF creates code duplication and sync ni

|0:35
Same microservice. 357MB vs 17MB. Which runtime pays for itself? #Go #Rust #Performance
SHORT
0:41
Same microservice. 357MB vs 17MB. Which runtime pays for itself? #Go #Rust #Performance

The same users microservice - identical endpoints, identical database โ€” running in three different runtimes: - ASP.NET under 200 concurrent requests: ๐Ÿฏ๐Ÿฑ๐Ÿณ๐— ๐—• - Go under 200 concurrent requests: 37MB - Rust under 200 concurrent requests: 17MB At idle, ASP.NET already costs 109MB just sitting ther

|0:41
Don't Use Singleton, Use Dependency Injection
SHORT
0:35
Don't Use Singleton, Use Dependency Injection

Singleton is global state dressed up as a best practice. If you're still using getInstance() in 2026, you're hiding bad dependency injection design. Here's why senior devs refuse it. #programming #designpatterns #singletons #dependencyinjection #softwarearchitecture #coding #backend #cleancode

|0:35
Most Teams Migrate to Kafka for the Wrong Reasons #systemdesign #devops
SHORT
0:35
Most Teams Migrate to Kafka for the Wrong Reasons #systemdesign #devops

Postgres handles 30K msgs/sec. 55% of Kafka users are under 1 MiB/s. The "database as queue" anti-pattern is actually the correct default for most startups. Here's when to actually migrate. #postgres #kafka #systemdesign #backend #devops

|0:35
Why 150MB container images are TRASH ๐Ÿ—‘๏ธ
SHORT
0:24
Why 150MB container images are TRASH ๐Ÿ—‘๏ธ

Go container: 15MB. Node container: 150MB. That's 6X smaller. Smaller means cheaper deployed. That's just math. Watch the full video for a detailed breakdown of the memory experiment! #golang #nodejs #memory #containers #docker #shorts #coding #backend #performance #devops

|0:24
STOP using lib/pq for go in 2026 ๐Ÿš€
SHORT
0:24
STOP using lib/pq for go in 2026 ๐Ÿš€

Use pgx instead. Pure Go, connection pooling, prepared statements. Or pgxpool for built-in connection pool. Production ready. Watch the full video for the full migration guide and performance benchmarks! #golang #nodejs #memory #containers #docker #shorts #coding #backend #performance #devops

|0:24
Node is as fast as Go? Cold Start TRUTH ๐Ÿคฏ
SHORT
0:24
Node is as fast as Go? Cold Start TRUTH ๐Ÿคฏ

Can Node.js cold starts keep up with Go? We tested it in an isolated container with real DB connections. Watch the long-form video on my channel for a detailed show on how we set up the experiment! Fight me in the comments! GitHub: https://github.com/prod-garbage-destroyer/cold-start-tax-experimen

|0:24
AI Agents Are Breaking Backend QA
SHORT
0:32
AI Agents Are Breaking Backend QA

Your AI agent didn't fail in one request. It failed across the entire workflow. Step two subtly hallucinates, and step five silently corrupts your database. Normal QA and standard logs are useless here. You don't need more unit tests. You need deterministic traces, semantic eval gates, and replayabl

|0:32
Your semantic evaluations are missing the entire problem ๐ŸŽฏ #AIMonitoring #Tech
SHORT
0:28
Your semantic evaluations are missing the entire problem ๐ŸŽฏ #AIMonitoring #Tech

Your cloud bill is paying for silent AI agent failures. Traditional APM is dead hereโ€”a 200 OK network request means nothing if the reasoning engine drops a production table. You need semantic evaluations mapped to LLM decision trees. Stop shipping agentic wrappers until your monitoring can evaluat

|0:28
POPULAR VS FAST | Quarkus vs Spring Boot Verdict (2026)
SHORT
0:51
POPULAR VS FAST | Quarkus vs Spring Boot Verdict (2026)

Spring Boot is the enterprise cathedral, but Quarkus is the cloud-native blade. In 2026, if you care about startup speed, container density, and cloud bills, there's only one winner. 00:00 - The Hook: Popular vs Fast 00:11 - Startup Speed: Native Battle 00:19 - Memory Massacre: 3x Density 00:27 - Th

|0:51
CEREMONY VS SPEED | Go vs Java Verdict (2026)
SHORT
0:41
CEREMONY VS SPEED | Go vs Java Verdict (2026)

Java is an enterprise tank, but Go is the speedrun language for teams that care about shipping. In 2026, the real bottleneck isn't concurrencyโ€”it's memory and deployment friction.

|0:41
FIREBASE FEELS EASY UNTIL... | Supabase vs Firebase (2026)
SHORT
0:41
FIREBASE FEELS EASY UNTIL... | Supabase vs Firebase (2026)

Benchmarked predictable pricing, exposed NoSQL query limitations, and explained why the choice between Supabase and Firebase is really just SQL vs proprietary lock-in. #Supabase #Firebase #SQL #NoSQL #SystemDesign #DevVerdict #2026 #WebDev #Backend #FullStack #IndieHacker #Shorts

|0:41

43 videos total