• Home
  • Journey
  • Decisions
  • Uses
  • Contact

Decisions

A log of the architectural choices behind the systems I have worked on. Each entry captures the context, the options on the table, and the reasoning that led to the final direction.

4 decisions documented

June 2025 Adopting Zero-Trust Connectivity for Node-to-Center Communication Distributed nodes required secure communication with the central platform without exposing services publicly. The absence of fixed IP addresses made inbound connectivity impossible...
architecturesecuritynetworkingdistributed-systems
Read decision
January 2025 Introducing an Edge Control Layer for Security Enforcement and Node-Aware Routing As the system grew, client traffic needed consistent security enforcement and predictable routing. Requests also increasingly needed to reach customer-specific nodes directly (when...
architecturesecurityapiscalability
Read decision
May 2024 Introducing a Reliable Transport Layer Between Nodes and the Central System As the system moved beyond pilot usage, distributed nodes began sending increasing volumes of device data to the central platform for further processing. The existing approach reli...
architecturescalabilitymessagingreliability
Read decision
January 2024 Choosing Incremental Evolution Over a Clean Rebuild A pilot system needed to transition into a production-grade platform. The existing implementation centered around a Node.js backend, which was suitable for rapid prototyping but no...
architectureevolutionplatform
Read decision
Design by Erland © 2026 Richárd Németh
Linkedin