About Javonet

Build single applications, modules or services created using modules from different technologies with native performance.

Javonet allows you to reference and use modules or packages written in Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python, JavaScript/TypeScript like they were created in your technology. It works on Linux/Windows and macOS for applications created in JVM, CLR/Netcore, Perl, Python, Ruby, NodeJS, C++ or GoLang.

Javonet Benefits

  • An extremely user-friendly framework for C#/J#/F#/VB.NET, Java, Clojure, Kotlin, Groovy, Perl, Python, Ruby, JavaScript, TypeScript, GoLang, C++ allowing to easily and instantly access any foreign module within same application or call public interfaces from modules on remote node
  • Reliable and secure solution suitable for projects of any size and complexity within all sector industries.
  • Remarkable speed advantage over traditional Web Services, providing an up to 20 000x faster performance making it an excellent choice for applications where speed and performance are critical factors.
  • Highest level of security by running entirely within the local machine in single OS process or remotely in cloud environment, containers or PaaS and IaaS services.
  • Reduces integration complexity and resource constraints by eliminating the need for technology changes or additional connectors. Removes the need for writing integration layer or web services.
  • Streamlines integration of UI, back-end components, and device SDKs across technologies.
  • Drastically cuts costs and reduces risks for businesses (saving huge amount of development time, testing, documentation, short time to market deployment).
  • Streamlines deployment and integration by combining the main application and external modules into a single package.

Javonet Features

  • Works for applications written in: C#/J#/F#/VB.NET, Java, Clojure, Kotlin, Groovy, Perl, Python, Ruby, JavaScript, TypeScript, GoLang, C++.
  • Runs on Windows, Linux and macOS.
  • Supports in-process integration of cross-technology modules as well as replaces the need for Web Services or gRPC for remote inter microservices integrations.
  • High Performance: Provides native high performance, which is crucial for real-time and resource-intensive applications. Reaches 20 000x higher performance within in-process integrations vs. Webservices and 70% higher performance for remote calls vs. Web services.
  • Lightweight Solution: It's packaged as a light single file, simplifying integration without adding significant overhead to the project. Can be easily added as simple dependency to any NodeJS, CLR, netcore, Python, Ruby, Perl, GoLang or C++ project.
  • No Proxy Generation: There is no need for proxy generation, streamlining the integration process.
  • User-Friendly API: Javonet provides an easy, fluent, reflection-style API, making it accessible even to those not deeply versed in integration specifics, without the need to understand details of foreign technologies used to build integrated modules.
  • Architecture Simplicity: For in-process integration solution does not rely on complex client-server or web services architectures, which simplifies deployment and reduces potential points of failure. For remote it provides clear direct calls to public interfaces without unnecessary duplication of those interfaces as REST or SOAP APIs.
  • Comprehensive Method Support: Supports a wide range of programming structures from all supported languages including public/staticmethods, value types and reference types, generics, ref and out arguments, events and much more ensuring compatibility and flexibility for any interface.
  • Cross-Technology Exception Handling: This feature ensures that exceptions are managed effectively across different programming environments.
  • Garbage Collector Integration: Javonet has built-in garbage collector propagation, which is essential for managing memory in applications.
  • Multi-threading support: ensures that applications build leveraging multiple-threads will get automatically created and maintained corresponding threads in runtimes running integrated modules.