[IGNITE-14382] Network module API structuring

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha2
• Component/s: networking
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Aleksandr Polovtsev
• Reporter: Sergey Chugunov
• Reviewer: Sergey Chugunov
• Created: 24/Mar/21 06:58
• Updated: 17/Jun/21 10:50
• Resolved: 12/Apr/21 12:26

Description

First version of the network module introduced a NetworkCluster interface providing access to all functionality of the module: sending and receiving messages in p2p fashion, topology API (current set of online nodes, node join and left events) and some lifecycle-related methods.

Further development has shown that it makes sense to gather these pieces of functionality under separate interfaces that should be accessible from NetworkCluster or similar single entry point.

Suggestions for naming of these interfaces: Topology and Messaging. Keeping lifecycle callbacks and methods under the same interface seems natural at the moment.

Issue Links

• links to: GitHub Pull Request #84