Skip to content
EN FR

P2P Architecture

Documentation status: architecture — see Maturity and evidence.

This page describes P2P as a communication-plane topology, not as an automatic property of every logiCells application.

Conceptual components

Peer
  -> identity
  -> trust domain / groups
  -> advertised capabilities
  -> communication endpoints
  -> routing state

A peer may host a local Runtime, expose selected capabilities, and consume capabilities from other peers. Discovery, routing, and replication details remain behind published communication contracts.

Boundaries

  • identity: peer identity is distinct from Runtime-object identity;
  • transport: several transports may support the same abstraction;
  • security: rights are evaluated independently from reachability;
  • state: routing and availability are dynamic;
  • data: replication must define convergence and conflict behavior.

Failures

The network must be treated as fallible. Calls may time out, be duplicated, or arrive after a topology change. Non-idempotent operations need suitable operation identifiers and recovery policies.

Governance

In organizational environments, trust domains and operational policy take precedence over simple technical peer discovery.