Architecture on Nalar

Designing Stateless Web Services for Horizontal Scaling

Tue, 01 Sep 2026 00:00:00 +0700

Horizontal scaling adds application replicas instead of making one machine larger. The load balancer can send each request to any healthy instance, which only works reliably when instances do not depend on unique local state.

“Stateless” does not mean the application has no state. It means durable or shared state lives outside an individual process so any replica can continue serving the workload.

Identify hidden local state

A service may appear stateless while depending on:

Evolving APIs Without Breaking Clients

Tue, 01 Sep 2026 00:00:00 +0700

An API is not only an HTTP path or function signature. It is a contract about syntax, semantics, timing, errors, ordering, defaults, and lifecycle.

Breaking changes often happen because a server remains syntactically compatible while changing one of those less-visible assumptions.

Safe API evolution starts by identifying what clients can reasonably depend on and designing changes that allow old and new versions to coexist.

Compatibility has multiple dimensions

A change can preserve JSON shape and still break clients.

Feature Flags Without Long-Lived Technical Debt

Tue, 01 Sep 2026 00:00:00 +0700

Feature flags decouple code deployment from feature release. A team can deploy dormant code, enable it for internal users, roll it out gradually, and disable it without rebuilding the application.

The cost is hidden control flow. Every long-lived flag creates another possible system configuration, and interacting flags multiply those configurations quickly.

The engineering goal is therefore not “use flags everywhere.” It is to make each flag temporary, observable, and owned.