We are on the process of creating an SDK for our thin(API) client.<p>Saw an article by TemproalIO - https://docs.temporal.io/blog/why-rust-powers-core-sdk/ which states the following:<p>"When it comes to connecting multiple languages to a shared library, the traditional choice is often C, but Rust makes for a safer and more modern alternative. Having language SDKs directly link to the Rust core meets our end-user-ease goal and keeps overhead low. There are other ways we could've tackled the problem (for example by running another process that communicates with the language-specific SDK over some kind of IPC), but those options probably fail our ease-of-use goal. If desirable, we can always run out-of-process later because we use Protobufs to represent data passed between the Core and language-specific SDKs. This technique also reduces the amount of duplicate code we would have to write for each new language. Rust also very easily compiles to WASM, which unlocks some very interesting possibilities..."<p>If you have already worked on a similar use-case, please share your experience.