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

Legacy codebases are hemorrhaging talent as maintainability collapses under the weight of unpatched dependencies and deprecated logic. We must confront the reality that staying on aging frameworks is a strategic failure. Here's why you need to migrate now. #programming #softwareengineering #archit

In this video, we break down exactly when a centralized control plane collapses under load, the exact cost curve of coordination vs. debugging, and how to use Choreography as a pressure relief valve at scale. š šŖšµš®š šš² š°š¼šš²šæ: - Control Plane Under Load (Kubernetes, Nginx, API Gateway) -

Rust abstractions look high-level, but compile into low-level machine code with near-C++ performance. Here's the proof through assembly, LLVM, and runtime metrics. #rust #systemsprogramming #performance #llvm #softwareengineering

Quick walkthrough of the benchmark repo structure: implementations, scripts, artifacts, and the wrk workload file used for fair comparison. Re-run it yourself: GitHub link in description. #shorts #zig #rust #cplusplus #backend #benchmark #opensource

Code-level proof cut: same routes, same schema, same wrk workload. Rust wins RPS, Zig wins p99, and C++ wins footprint in this run. Full repo and artifacts: GitHub link in description. https://github.com/prod-garbage-destroyer/zig-rust-cpp-cloud-v1 #shorts #zig #rust #cplusplus #backend #benchmark

Same API, same workload, same environment. Rust leads throughput, Zig leads p99 latency, C++ leads footprint. Full benchmark and code: GitHub link in description. https://github.com/prod-garbage-destroyer/zig-rust-cpp-cloud-v1 #shorts #zig #rust #cplusplus #backend #benchmark #cloud

I benchmarked the same cloud API implementation in Zig, Rust, and C++ with identical routes, schema, workload, and environment. In this video we compare: - Throughput under c=100, c=250, c=500 - Tail latency (p99) behavior under load - Operational footprint (image size + memory) - Real source files

#WebAssembly #Javascript

Most teams chase tiny throughput differences and ignore what actually impacts production. - Throughput delta: small - Container delta: massive - Memory delta: meaningful at scale Rust wins developer velocity and safety. C++ wins runtime efficiency and footprint. Pick based on your constraints. #ru

Rust and C++ are almost tied on throughput (~40K req/s), but not on operational cost. - Rust image: 114MB - C++ image: 18.6MB (84% smaller) - Rust memory: 4.3MB RSS - C++ memory: 2.5MB RSS (42% less) Verdict: choose constraints, not benchmark hype. Full benchmark + methodology in long video. #rust

Are you subsidizing Python's Global Interpreter Lock with your cloud bill? Python optimizes for the developer. Go optimizes for the machine. Stop writing core infrastructure in a scripting language. Pick Python for the algorithm. Pick Go for the backend. Drop your stack below š

I benchmarked Rust (Axum) and C++ (Drogon) for cloud REST APIs with PostgreSQL JSONB workloads. Performance is nearly identical (3-5% difference), but operational costs differ wildly. šš²š š³š¶š»š±š¶š»š“š: - Throughput: 38-42K req/s (Rust) vs 39-40K req/s (C++) ā statistically equivalent - Conta
93 videos total