About
JM Valino
IoT Architect & Platform Engineer
I design and build cloud-native systems for connected devices — spanning device onboarding and ingestion, edge gateways, event-driven processing, and the telemetry pipelines that move data at scale.
My focus is the architecture that keeps these systems honest as they grow: clear ingestion boundaries, decoupled hot paths, multi-tenant isolation, and platforms that teams can actually operate. I work primarily in TypeScript and NestJS on AWS, with AWS IoT Core at the center of most device-facing systems.
I also spend time on the harder edges of the domain — device provisioning at scale, edge gateway patterns for constrained networks, and event-driven runtimes for modeling device state at fleet scale.
Approach
how I think about systems
Architecture is a series of tradeoffs
There are no free wins — only decisions with consequences. The job is to make the consequences explicit and choose deliberately.
Design for the second hundred thousand devices
The first device is easy. Onboarding, rotation, observability, and blast radius are what decide whether the system survives growth.
Decouple the hot path
Ingestion should never be hostage to storage or downstream processing. Buffers and event-driven boundaries earn their keep under load.
Operable beats clever
A system you can observe, reason about, and change safely is worth more than one that is elegant on paper and opaque in production.
Toolkit
what I work with
- TypeScript
- NestJS
- Node.js
- AWS
- AWS IoT Core
- MQTT
- Event-driven architecture
- Telemetry pipelines
- Multi-tenant platforms
- Time-series & observability
Contact
Let's talk
Working on connected devices, edge systems, or telemetry at scale? I'd be glad to hear about it.
get in touch