What prevents you from deploying the application within the same K8
environment as a pod? If the thick client and the servers are within the
same network then you won't have any hurdles at all. That's the best
approach.
Otherwise, you need to a) expose K8 network if you want to connect from a
Hello!
You can surely use REST from .Net, but writing code for such use is left as
exercise for reader.
You can also use .Net thin client, with API & description available in docs:
https://apacheignite-net.readme.io/docs/thin-client
Regards,
--
Ilya Kasnacheev
ср, 13 нояб. 2019 г. в 01:43,
Thanks Ilya,
Am i able to use the .NET API in this way? Connecting to a remote cluster?
I am finding the documentation of the configuration a little hard to
understand in regards to the options for connection. In the Kubernetes YAML
file I see ports for REST, SQL and thin clients, would you use
Hello!
Well, you have a multitude of options here:
Thick client is not recommended since it is a part of topology and it may
suffer in case your desktop becomes disconnected, for example.
You can use REST all right. REST can execute services' methods, and you can
write services to do anything
I am new to Ignite and am struggling to figure out how to connect my client
application to my Ignite cluster hosted in Azure Kubernetes.
Effectively I want to remotely connect, that is, I dont want my client
machine to be in the topology, its probably not even in the same country, I
would like to
