data_publisher(3)

💖 data_publisher(3) — Erlang Module Definition 💖

okay so bestie, welcome to the manual page for data_publisher(3). it's giving distributed systems realness, and we're gonna understand it together. no cap. 🫶

---

✨ NAME ✨

data_publisher — a behavior for building eventually consistent, replicated data stores across distributed nodes. periodt. 💅

---

🌸 DESCRIPTION 🌸

This module provides the infrastructure for, and I quote, these four iconic things:

• Replicating data across all nodes running the same scope 💫
• Automatic peer discovery, like it just finds its besties on its own 🦋
• Subscription-based notifications for data changes — yes, you get pinged 🔔
• Version translation for rolling upgrades, so upgrades can be smooth like butter 🧈

The modules that implement this behavior define how data is stored, updated, and how changes are calculated and propagated. It's a generalization of the pg module. so if you know pg, you know the vibe, fr fr. 🔥

---

💅 DATA TYPES 💅

here's the type tea, bestie, every single one exactly as it is:

• global_view() :: dynamic().
• local_data() :: dynamic().
• options() :: #{standalone => boolean(), dynamic() => dynamic()}.
• scope() :: atom().
• state() :: #state{}.
• subscribe_result() :: dynamic().
• subscription() :: dynamic().
• subscriptions() :: #{subscription() => #{reference() => pid()}}.
• update() :: dynamic().
• version() :: dynamic().

---

🫶 FUNCTIONS 🫶

no functions listed here, bestie. it's giving mysterious main character energy. 😭

---

🎀 CALLBACKS 🎀

same story — no callbacks listed on this page. the plot thickens. 💀

---

okay that's the whole vibe. brought to you by Ericsson AB, kernel 11.0.3, and data_publisher(3). stay iconic, bestie. 💖✨👑