Working with collections
This article provides an introduction to cross-technology handling of collections. Data structures are one of the essential aspects of every piece of software. Any application constantly process various information, that very often require specific grouping and access strategies. This aspect is addressed by arrays and more advanced collection types. By using the Javonet framework, users gain ability to easily and effectively work with data structures originating from .NET Framework DLL. Every collection from .NET Framework DLL is treated as reference.
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 collections from .NET Framework DLL like they were available in any language but invocation must be performed through Javonet SDK API.
Working with lists
Javonet SDK contains various methods to interact with lists and consume the results in any language:
Select language you code in:
In the snippet above, list specific to called technology framework is created.
Then, some elements are added to the list.
Finally, this list can be handled through Javonet SDK, f.e. with getIndex method.
Working with dictionary
Javonet SDK contains various methods to interact with dictionaries and consume the results in any language:
Select language you code in:
In the snippet above, list specific to called technology framework is created.
Then, some elements are added to the list.
Finally, this list can be handled through Javonet SDK, f.e. with getIndex method.
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 .NET Framework DLL 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?