[
https://issues.apache.org/jira/browse/IGNITE-16332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov updated IGNITE-16332:
------------------------------------
Description: At this moment, every message in the cluster is sent via
scalecube cluster which brings scalecube message's overhead and some threading
implications. We can reuse ConnectionManager and implement messaging without
scalecube that still conforms the MessagingService API. (was: At this moment,
every message in the cluster is sent via scalecube cluster which brings
scalecube message's overhead and some threading implications. We can reuse
ConnectionManager and implement messaging without scalecube that still conforms
the MessagingService API.
Also "weakSend" method for MessagingService should be reintroduced )
> Implement messaging service without scalecube cluster
> -----------------------------------------------------
>
> Key: IGNITE-16332
> URL: https://issues.apache.org/jira/browse/IGNITE-16332
> Project: Ignite
> Issue Type: Task
> Components: networking
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Labels: ignite-3
>
> At this moment, every message in the cluster is sent via scalecube cluster
> which brings scalecube message's overhead and some threading implications. We
> can reuse ConnectionManager and implement messaging without scalecube that
> still conforms the MessagingService API.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
