https://github.com/sjsakib/ffirpc
Compile golang gRPC service to C shared library or WebAssembly and consume form multiple languages through FFI
https://github.com/sjsakib/ffirpc
dart ffi golang grpc shared-module
Last synced: 7 months ago
JSON representation
Compile golang gRPC service to C shared library or WebAssembly and consume form multiple languages through FFI
- Host: GitHub
- URL: https://github.com/sjsakib/ffirpc
- Owner: sjsakib
- License: gpl-3.0
- Created: 2025-06-15T15:22:22.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-07-28T16:51:46.000Z (8 months ago)
- Last Synced: 2025-07-28T18:34:54.483Z (8 months ago)
- Topics: dart, ffi, golang, grpc, shared-module
- Language: Dart
- Homepage:
- Size: 6.8 MB
- Stars: 2
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# FFI RPC
An experimental Go library that enables gRPC services to be consumed from multiple programming languages using Foreign Function Interface (FFI) through WebAssembly or C shared library.
## Overview
FFI RPC allows developers to:
- Write gRPC services in Go
- Compile them to WebAssembly or C shared libraries
- Call them from Node.js, Dart, and other languages that support WASM or FFI
- Bypass network overhead for local inter-language communication
## But why?
The primary purpose is to see if this could be done. Use cases where it could be useful:
- You have some shared business logic that you would like write once in Go and call from multiple languages, specially if you need to support offline functionality
So why involve gRPC and not just regular FFI?
- Defining, Encoding, Decoding the request and response types can be a pain
- Hope is that protobuf will be faster than encoding/decoding the data with json despite the overhead of gRPC
- Easy code generation for the consumers, whereas with regular FFI, wrappers or bindings have to be written/generated
- If written as a service, can easily be exposed to the internet for environments where FFI is not available or practical
## Project Structure
```
├── ffirpc.go # Core FFI RPC server implementation
├── ffirpc-js.go # Core FFI RPC server implementation for JavaScript/WebAssembly
├── clients/ # Client libraries for different languages
│ ├── node/ # Node.js/TypeScript client
│ └── dart/ # Dart client
└── example/ # An example service and its consumers
├── example.proto # Protocol buffer definition
├── proto-gen/ # Generated protocol buffer code
├── service.go # Service implementation
├── main.go # Entrypoint for server (C shared library)
├── main-wasm.go # Entrypoint for WebAssembly server
└── consumers/ # Example client implementations
├── node/ # Node.js consumer
└── dart/ # Dart consumer
```
## Running the example
### Compile the go service
```bash
cd example
make build
```
### Run the dart consumer
```bash
cd example/consumers/dart
dart main.dart
```
### Run the node consumer
Build the node library
```bash
cd clients/node
npm install
npm run build
```
Run the node consumer
```bash
cd example/consumers/node
tsx index.ts
```