@jnbridge
Java/.NET integration experts. Bridging the JVM and CLR since 2001.
Nothing here yet.
May 8 · 10 min read · Hashnode readers tend to care about the practical boundary: what actually happens when a Java library and a .NET library have to live in the same product? This version focuses on the implementation choices teams can ship — process wrappers, REST/gRPC...
Join discussion
May 5 · 6 min read · If you have ever built a Linux .so on your dev machine, copied it to older hardware, and watched it fail with a loader error, this one is familiar. Hashnode readers who ship native components, embedded deployments, or Java/.NET integrations with nati...
Join discussion
May 1 · 7 min read · If you have a Java service on one side and a .NET service on the other, “just pass the object across” turns into an architecture decision pretty quickly. Hashnode readers usually see this in real systems: a Spring app that needs a C# rules engine, an...
Join discussion
Apr 28 · 4 min read · Some production bugs are not really “your code” bugs — they’re dependency-chain bugs hiding underneath the runtime. This one is a good example: an x86 shared-memory setup crashes with an access violation, but the actual cause is a missing native DLL ...
Join discussion
Apr 24 · 4 min read · If you started with Shared Memory and now need your .NET and Java components on separate hosts, TCP is the next step. The move is straightforward, but there are a few settings that matter a lot in production: startup order, SSL, and access controls. ...
Join discussion