Nova on jdcsen

gRPC Bidirectional Streaming for a C++ Node-Graph Framework

Thu, 01 Jan 1970 00:33:44 +0000

Nova Sonic needed the speech framework’s pipelines delivered as a containerized gRPC service: audio and system prompts streaming in, inference requests streaming out. The team’s code had only ever been called through JNI.
Mapped gRPC C++’s bidirectional-streaming reactor onto the framework’s pipe abstraction once, as a reusable layer covering session setup and teardown, signal handling, graceful error handling and logging.
A new service needs under 300 lines of integration code: which pipe input receives request messages, and which pipe outputs become response messages. Adopted org-wide as the standard way to deploy a pipeline.
Established Protobuf and gRPC generated code as first-class CMake libraries in the framework’s build, so the same generated types are consumed by the pipeline’s nodes and by the server without duplicate-symbol conflicts.

Thu, 01 Jan 1970 00:33:44 +0000

Python provisioning system that stands up the complete Nova Sonic inference stack on one developer machine.
Deploys several Triton model containers plus the C++ node-graph orchestrator, wired together and ready to take speech-to-speech traffic.
Took a fifteen-person team from sharing a couple of hand-built demo environments to every engineer having their own.
Same pattern as L3Dockerize: make the right environment the cheap one.

Thu, 01 Jan 1970 00:33:43 +0000

Nodes in the C++ stream-processing framework behind Nova Sonic register themselves in a global registry through static initialization. No central list to edit, no explicit dependency from tools on the nodes they might load.
Registry is a thread-safe, function-local static constructed on first use, so registration is safe regardless of static initialization order across translation units.
Registration works by linking a node library or by LD_PRELOADing it. The development CLI can assemble a graph from a JSON definition using nodes it was never compiled against.
Pulled double duty as a dependency-inversion mechanism: consumers depend on the node interface, not on implementing libraries. Adopted across the organization and later picked up for embedded speech processing.