NATS & RPC Mechanisms

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

If you were building a system with multiple components that communicate over NATS, how would you approach that? We're trying to gauge where the interest would be regarding a Synadia created Google Proto Buffer (GPB) tool which would create multi-language bindings across JavaScript, Go, C, Python etc. The result would be defined payload structures and ease of communication between NATS connected components, from the browser, to the data centre, to the tiny edge.

How do you connect multiple components together for your NATS powered projects? *

We already use GPB with our custom tools

Ship JSON between our components and our teams use a version controlled JSON schema to help maintain integrity

Ship JSON between NATS connected client components and hope for the best

Other:

Are you familiar with GPB or do you use it? *

Familiar and use it

Familiar but don't use it

Heard of it

What is GPB?

How would you prefer use a tool which created multi-language bindings for your projects? *

Copy and paste my .proto file into the browser and download the generated assets

Run the tool in my tool chain as a CLI component

Both the simple SaaS service and CLI tool

Other:

What languages do you think are key for this tool? *

C++

C# / .net

JavaScript

Java

Python

Rust

TypeScript

Other:

Required

Would you expect this to be open source? *

Yes

Don't care

Submit

Clear form

Never submit passwords through Google Forms.

This form was created inside of Synadia. Report Abuse

Forms