Javonet integrates Java and .NET allowing at the same time for seamless usage of both technologies directly from one another. The technology has been developed with the focus on safety. The biggest advantage of Javonet against the web services apart from the difference of how much faster it is from web services is the safety. Javonet works in a single OS process which makes is proof of any middle man attacks or any other communication disruptions.
How the single OS process integration works?
When Javonet starts it loads side by side the required runtime either JVM or CLR within the calling single OS process. This way of integrating two runtimes is called Runtime Bridging. In both runtimes the Javonet module is responsible of handling the seamless, native communication between two of them. As a result your application is using the external technology libraries just as if they were natively called.
One OS process works just like a single application exchanging all the data in a fraction of the second. This allows for achieving the highest performance of 250 000 calls per second and the overhead of not more than nine millionth of a second!
The Javonet module is handling all the crucial operations like thread synchronization or Garbage collection on both runtimes. The key of the Javonet performance is that all the .NET code is handled by .NET Framework whereas all the Java code is handled by the JVM. This allows for unbeatable reliability and makes Javonet the solution for the crucial implementations.
