3 ms·
Show HN: LibPolyCall – Zero-Trust Polyglot FFI with Perfect State Reproduction
Hi HN! I'm Nnamdi from OBINexus Computing. I've been working on LibPolyCall, a program-first protocol that eliminates language barriers in distributed systems.
The Problem: Every API needs separate implementations for Python, Node.js, Java, etc. This creates duplicate code, maintenance nightmares, and debugging hell across microservices.
Our Solution: LibPolyCall provides:
Single API definition → automatic polyglot implementations
Zero-trust security at the protocol level
Cryptographically-seeded GUIDs for perfect bug reproduction
Silent telemetry capturing every interaction
Hot-swappable adapters without downtime
Key Innovation: We've moved from "binding-first" to "program-first" architecture. Instead of writing language-specific bindings, you define your API once and LibPolyCall handles the translation.
Real Metrics:
Reduced integration time by 75% in pilot deployments
Zero-overhead FFI calls through direct memory mapping
100% state reproducibility for debugging
Supports Python, Node.js, Rust, Go (more coming)
Use Cases:
Legacy COBOL systems talking to modern microservices
Cross-language microservice communication
Unified telemetry across polyglot systems
Hot-swapping components without downtime
Currently in v1trial. Looking for feedback from teams dealing with polyglot complexity.
GitHub: https://github.com/obinexus/libpolycall https://github.com/obinexus/libpolycall
Docs: github.com/obinexus
/libpolycall/docs
Video Demo: ionhttps://youtube.com/@obinexus/playlists https://youtube.com/@obinexus/playlists (search libpolycall)
Happy to answer questions about the architecture, zero-trust implementation, or our approach to solving the polyglot problem!