Reddit Programming

What’s the most cost-efficient way to run a persistent WebSocket API with auto-scaling and real-time traffic?
https://www.reddit.com/r/programming/comments/1o71amc/whats_the_most_costefficient_way_to_run_a/

I’ve been working on a real-time backend in Go (Gin) that bridges VS Code extensions and mobile clients via WebSocket connections.
The API handles device pairing, authentication, and real-time messaging — acting as a discovery and message broker service between desktop and mobile. Current Architecture Language: Go 1.21 Platform: Google Cloud Platform (auto-scaling instance group) Load Balancer: GCP HTTP(S) LB with sticky sessions (CLIENT_IP affinity) Database: Firestore (NoSQL, auto-scaling) Concurrency: ~200 sockets per instance, up to 3 000 total Scaling Trigger: 75 % CPU utilization Cost Range: $27 – $60 / month Design: Fill-then-spill auto-scaling, in-memory message broker per instance TLS: Google-managed SSL certificates The setup performs well — instances scale automatically, sticky sessions maintain WebSocket persistence, and Firestore handles durable state.
But I’m exploring whether a single Hetzner CPX server could handle the same load more cost-efficiently without losing too much reliability. Programming & Architecture Questions For those who’ve built similar real-time Go or WebSocket systems: How do you decide when to scale out (multi-instance) versus scale up (single powerful node) for concurrent Go services? Have you found Hetzner or similar bare-metal providers more cost-effective for steady WebSocket workloads? Each instance in my design maintains its own message broker and token cache; Firestore stores persistent data. Sticky sessions avoid cross-node coordination — are there hidden scaling pitfalls in this approach? Would adding Redis Pub/Sub or a lightweight state bus actually improve reliability, or just increase complexity and cost? For long-lived WebSockets, has anyone found Kubernetes or Cloud Run cheaper in practice than manually managed VMs? I’m mainly trying to balance cost, reliability, and architectural simplicity as the system scales.  submitted by /u/vscoderCopilot (https://www.reddit.com/user/vscoderCopilot)
[link] (https://github.com/emirbaycan/vscoder-copilot) [comments] (https://www.reddit.com/r/programming/comments/1o71amc/whats_the_most_costefficient_way_to_run_a/)

3 views05:57

Reddit Programming

How Modern Compilers Optimize Code A Walkthrough
https://www.reddit.com/r/programming/comments/1o722wo/how_modern_compilers_optimize_code_a_walkthrough/

submitted by /u/CockroachFair4921 (https://www.reddit.com/user/CockroachFair4921)
[link] (https://www.yourquorum.com/question/how-modern-compilers-optimize-code-a-walkthrough?utm_source=reddit_sh&utm_medium=social_sh&utm_campaign=reddit_sh) [comments] (https://www.reddit.com/r/programming/comments/1o722wo/how_modern_compilers_optimize_code_a_walkthrough/)

3 views06:04

Reddit Programming

I am a programmer, not a rubber-stamp that approves Copilot generated code
https://www.reddit.com/r/programming/comments/1o729o1/i_am_a_programmer_not_a_rubberstamp_that_approves/

submitted by /u/pyeri (https://www.reddit.com/user/pyeri)
[link] (https://prahladyeri.github.io/blog/2025/10/i-am-a-programmer.html) [comments] (https://www.reddit.com/r/programming/comments/1o729o1/i_am_a_programmer_not_a_rubberstamp_that_approves/)

3 views06:17

Reddit Programming

Construí en una noche una app para seguir mis postulaciones de trabajo. Se llama jobGetsJob y quiero feedback real
https://www.reddit.com/r/programming/comments/1o711py/constru%C3%AD_en_una_noche_una_app_para_seguir_mis/

Anoche me pintó el bichito de construir algo rápido.
Tenía una idea que venía dando vueltas hace rato, y dije: “bueno, basta de pensarlo, lo hago”. Así que en una sola noche armé jobGetsJob, una app para seguir todas las postulaciones laborales y tener tu búsqueda de trabajo ordenada como si fuera un proyecto. La idea es simple, casi obvia: conseguir trabajo también es un trabajo, y si uno puede organizar su código, ¿por qué no organizar sus postulaciones igual? No es más que un MVP, una primera versión, algo para probar si realmente hace falta.
Por eso lo subí online y quiero feedback real, sin filtro.
¿Te parece útil? ¿Le falta algo? ¿Lo usarías si estás buscando laburo? Podés entrar y probarlo acá 👇 https://jobgetsjob.vercel.app/  submitted by /u/fertejo20 (https://www.reddit.com/user/fertejo20)
[link] (https://jobgetsjob.vercel.app/) [comments] (https://www.reddit.com/r/programming/comments/1o711py/constru%C3%AD_en_una_noche_una_app_para_seguir_mis/)

3 views06:51

Reddit Programming

Reverse Engineering iWork (So You Don't Have To)
https://www.reddit.com/r/programming/comments/1o78acf/reverse_engineering_iwork_so_you_dont_have_to/

submitted by /u/AndrewMD5 (https://www.reddit.com/user/AndrewMD5)
[link] (https://andrews.substack.com/p/reverse-engineering-iwork) [comments] (https://www.reddit.com/r/programming/comments/1o78acf/reverse_engineering_iwork_so_you_dont_have_to/)

1 view02:29

Reddit Programming

Unpacking Cloudflare Workers CPU Performance Benchmarks
https://www.reddit.com/r/programming/comments/1o7nads/unpacking_cloudflare_workers_cpu_performance/

Cloudflare addressed benchmarks that showed Workers slower than Vercel in CPU-heavy tasks. They traced the gap to V8 tuning, scheduling, and inefficiencies in libraries and adapters. Fixes included better isolate scheduling, memory tuning, and optimizations to OpenNext and JSON.parse. They also pushed upstream improvements to V8 and Node.js. As a result, Workers now perform on par with Vercel in most tests and much closer in the remaining ones, while Cloudflare continues to refine performance.  submitted by /u/Happy_Junket_9540 (https://www.reddit.com/user/Happy_Junket_9540)
[link] (https://blog.cloudflare.com/unpacking-cloudflare-workers-cpu-performance-benchmarks/) [comments] (https://www.reddit.com/r/programming/comments/1o7nads/unpacking_cloudflare_workers_cpu_performance/)

1 view02:32

About

Blog

Apps

Platform