{"_id":"58e6b70a85ec873100be975a","project":"5612c2a00fbdb60d00e4c7d1","user":"5612c290c0731b0d00625078","__v":0,"parentDoc":null,"version":{"_id":"5612c2a00fbdb60d00e4c7d4","__v":7,"project":"5612c2a00fbdb60d00e4c7d1","createdAt":"2015-10-05T18:34:08.611Z","releaseDate":"2015-10-05T18:34:08.611Z","categories":["5612c2a10fbdb60d00e4c7d5","58e6b64bc397de1b00173c09","58e6b68eb1eece19008b81fe","58e6b6d185ec873100be9734","58f5e5c2616bbb1b00d54c15","58f5eaa74c413f19007a2858","58f767a79c723f19004e1ca9"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"0.0.1","version":"0.0.1"},"category":{"_id":"58e6b6d185ec873100be9734","project":"5612c2a00fbdb60d00e4c7d1","version":"5612c2a00fbdb60d00e4c7d4","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-04-06T21:44:49.026Z","from_sync":false,"order":3,"slug":"cluster-operations","title":"Partisan"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-04-06T21:45:46.948Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"Partisan provides several pluggable backends:\n\n* `partisan_default_peer_service_manager`: full membership, where all nodes maintain active connections to all other nodes in the system.\n* `partisan_client_server_peer_service_manager`: star topology, where clients communicate with servers, and servers communicate with other servers\n* `partisan_hyparview_peer_service_manager`: modified implementation of the HyParView protocol, peer-to-peer, designed for high scale, high churn environments\n* `partisan_static_peer_service_manager`: static membership, where connections are explicitly made between nodes\n\nTo change the peer service manager, simply use the API provided by Partisan.  Once changed, the application will have to be restarted for the change to take effect.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"> partisan_config:set(partisan_peer_service_manager, partisan_default_peer_service_manager).\\nok\",\n      \"language\": \"erlang\"\n    }\n  ]\n}\n[/block]","excerpt":"Partisan provides several backends for peer service operations.","slug":"partisan","type":"basic","title":"Backends"}

Backends

Partisan provides several backends for peer service operations.

Partisan provides several pluggable backends: * `partisan_default_peer_service_manager`: full membership, where all nodes maintain active connections to all other nodes in the system. * `partisan_client_server_peer_service_manager`: star topology, where clients communicate with servers, and servers communicate with other servers * `partisan_hyparview_peer_service_manager`: modified implementation of the HyParView protocol, peer-to-peer, designed for high scale, high churn environments * `partisan_static_peer_service_manager`: static membership, where connections are explicitly made between nodes To change the peer service manager, simply use the API provided by Partisan. Once changed, the application will have to be restarted for the change to take effect. [block:code] { "codes": [ { "code": "> partisan_config:set(partisan_peer_service_manager, partisan_default_peer_service_manager).\nok", "language": "erlang" } ] } [/block]