SShortSingh.
Back to feed

Why a Developer Chose a Long-Lived Node Process Over Serverless for Real-Time Apps

0
·42 views

A developer building a live dashboard with thousands of persistent connections chose a long-lived Node.js process over a serverless architecture, arguing that serverless economics are fundamentally misaligned with real-time workloads. While serverless excels at short request-response tasks, its pricing model charges per invocation and connection-minute, making it costly for applications that maintain continuous open connections. Running an in-process state model eliminated repeated Redis round trips and turned fan-out to thousands of subscribers into a simple memory loop instead of thousands of billable calls. The trade-off required roughly a week of additional infrastructure work — covering graceful draining deploys, manual scaling decisions, and memory management — paid once upfront. The developer's broader takeaway is that engineers should identify the core constraint of their product before defaulting to the most popular architectural recommendation.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Zoom Windows clients flagged for high-severity certificate validation flaw, CVE-2026-108184

Zoom disclosed CVE-2026-108184 on October 13, 2026, as bulletin ZSB-26021, describing improper certificate validation in certain Windows clients. The issue carries a CVSS 3.1 score of 7.4 and can be triggered over the network without privileges or user interaction, though attack complexity is high. Zoom says the flaw may allow unauthenticated information disclosure, and the bulletin rates confidentiality and integrity impact as high without detailing the exact attack path. The affected products include Zoom Workplace for Windows, Zoom Workplace VDI Client, and Zoom Rooms for Windows across listed version ranges. The article cautions that a ZoomEye count of 347,617 Zoom fingerprints does not indicate how many clients are vulnerable, and recommends authenticated endpoint inventory to decide which systems need patching.

0
ProgrammingDEV Community ·

A Method for Reading Code You Didn't Write: Run, Enter, Follow, Break

Reading unfamiliar code is often approached by opening files at random, which wastes days and rarely builds real understanding. The article argues that reading is a learnable skill that matters more than writing, since most engineering work involves understanding existing code. It proposes a four-step method: run the program first, locate its entry point, trace a single execution path, and deliberately break something to see what fails. A fifth habit, consulting the project's history, is also recommended. The approach is illustrated with serverctl, a Go terminal UI for administering Linux servers over SSH, whose 107 Go files make it a useful example.

0
ProgrammingDEV Community ·

Repetitive Tasks, Not Low Productivity, May Be the Real Drag on Teams

The article argues that many teams struggle less with overall productivity than with repetitive, rule-based work. Tasks such as moving data between tools, sending routine follow-ups, compiling reports, and triaging requests consume significant hours without needing human judgment. The author, an automation developer, points to n8n, an open-source, low-code workflow platform, as one way to address this. Highlighted advantages include integrations with hundreds of apps, self-hosting for data control, and built-in support for AI models and agents. The piece suggests that the real benefit of automation is freeing staff for strategy, creativity, and client relationships.

0
ProgrammingDEV Community ·

Java String.format() Behaves Differently Under German Locale Settings

A developer found that String.format("%.2f", 0.5) produces "0,50" on a laptop with German regional settings, which then causes Double.parseDouble to throw a NumberFormatException. The article explains that string formatting in Java builds text from templates whose format specifiers such as %d, %s and %.2f are replaced by argument values. It compares the methods that produce this output, including String.format(), String.formatted() added in Java 15, System.out.printf() and the Formatter class. It also notes that all of these share the same template syntax and that locale settings such as German or French change the decimal separator from a point to a comma.