[
https://issues.apache.org/jira/browse/IGNITE-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153598#comment-17153598
]
Denis A. Magda commented on IGNITE-13013:
-----------------------------------------
Anton,
In my experience, the client-to-client connectivity option is expected in the
micro-services architectures. But usually high-level frameworks and protocols
are used for inter-service communication. Certainly, there are usage scenarios
of Ignite services and messaging APIs as well, however, those are not
widespread and might be safely disregarded (especially in cloud environments
that go with similar well-integrated APIs).
Personally, I would use the forceClientToServer for both things. It’s even
better to create an Azure function and check that disabling of the
communication server socket is the only thing we need. There might be something
else hidden which can influence another configuration way/option.
> Thick client must not open server sockets when used by serverless functions
> ---------------------------------------------------------------------------
>
> Key: IGNITE-13013
> URL: https://issues.apache.org/jira/browse/IGNITE-13013
> Project: Ignite
> Issue Type: Improvement
> Components: networking
> Affects Versions: 2.8
> Reporter: Denis A. Magda
> Priority: Critical
> Fix For: 2.9
>
>
> A thick client fails to start if being used inside of a serverless function
> such as AWS Lamda or Azure Functions. Cloud providers prohibit opening
> network ports to accept connections on the function's end. In short, the
> function can only connect to a remote address.
> To reproduce, you can follow this tutorial and swap the thin client (used in
> the tutorial) with the thick one:
> https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial
> The thick client needs to support a mode when the communication SPI doesn't
> create a server socket if the client is used for serverless computing. This
> improvement looks like an extra task of this initiative:
> https://issues.apache.org/jira/browse/IGNITE-12438
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
