Use static fields and properties from any runtime in GoLang app
This article provides an introduction to cross-technology handling of static fields and properties.
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. If have not yet created your first project check Javonet overview and quick start guides for your technology.
With Javonet you can interact with static field and properties from any runtime like they were available in GoLang but invocation must be performed through Javonet SDK API.
Custom any runtime with static fields and properties
With Javonet it is possible to reference any custom any runtime and interact with public static fields and properties declared on types defined within that module almost the same as with any other GoLang library.
Snippet below represents the sample code from any runtime which contains class with fields:
Select technology of module you want to use:
It is possible to get one of the declared static fields from any runtime using following GoLang code.
Select technology of module you want to use:
This uses in memory runtime bridging to load the any runtime, and next retrieves reference to specific type and gets the static field. Result of the invocation is returned as regular GoLang value and can be used for further processing. It is possible to set one of the declared static fields from any runtime using following GoLang code.
Select technology of module you want to use:
This uses in memory runtime bridging to load the any runtime, and next retrieves reference to specific type, then sets and gets the static field. Result of the invocation is returned as regular GoLang value and can be used for further processing.
Framework static fields and properties
The same steps are required to get types and fields from framework any runtime:
Select technology of module you want to use:
The same operation can be performed remotely by just changing the new Runtime Context invocation from in memory to tcp that will create and interact with your any runtime objects on any remote node, container or service that hosts Javonet Code Gateway. This way you can preserve the same logic in your application and instantly switch between monolithic and microservices architecture without the need to implement the integration layer based on web services or other remote invocation methods.
Read more about use cases and software architecture scenarios where Javonet runtime bridging technology can support your development process.
Was this article helpful?