Technical Product Manager | Platforms, Infrastructure & AI Systems
Binil V Jacob
I build complex technical products - software platforms, cloud infrastructure, and connected hardware - from 0→1.
My journey spans cloud platforms, blockchain systems, R&D product development, and connected hardware - from smart lighting protocols to production device fleets. I specialize in designing scalable architectures and translating complex technical systems into usable products.
Product Case Studies
Case studies covering product strategy, key decisions, technical architecture, and outcomes.
Product Decisions & Systems Thinking
Key architectural and product insights derived from real-world implementations.
Choosing a messaging protocol for real-time, constrained environments
I chose MQTT over HTTP polling for real-time device-state synchronization. Tradeoff: it requires persistent broker connections, which are more memory-intensive than stateless HTTP. Result: lightweight, reliable messaging that stayed fast even over constrained, high-latency networks.
Event-driven architecture over polling for automation workflows
I chose an event-driven pipeline over scheduled polling to drive automation workflows. Tradeoff: more architectural complexity than a simple polling loop. Result: standard operations and trigger-based actions scale independently, so user-defined workflows execute immediately when input state changes.
Local processing over full cloud execution for reliability
I chose to run routine automation logic locally on edge hubs rather than round-tripping every decision through the cloud. Tradeoff: added complexity in keeping local and cloud state in sync. Result: guaranteed privacy and continued operation during internet outages, while the cloud layer still handles scale, analytics, and third-party integrations (like Alexa/Google Home).
Decentralized storage over a central database for verification
I chose IPFS-based decentralized storage over a centralized database for issued certificates. Tradeoff: an added dependency on IPFS availability instead of one simpler datastore. Result: immutability across distributed nodes made credentials tamper-evident and cryptographically verifiable without relying on a single authoritative database.