On the local node
- Accepted envelopes and delivery state remain in the local Relay store.
- Workers can retry pending routes without changing the producer application database.
Wizaya Server Suite
PBB Relay
Selective store-and-forward delivery for approved messages and operational events between configured PBB nodes.
What it is
A service in the local-node foundation
Integrated · Production hardening
Baseline node service
PBB Relay accepts approved message envelopes, persists them locally, and retries delivery through configured routes. It supports selected inter-node workflows without requiring every application database to stay continuously connected.
Relay is a message transport, not universal database replication. Each producer and consumer owns its message contract, authorization, idempotency, retention, and business-state handling.
Node role
What it contributes
Provides durable selective delivery between known endpoints so supported workflows can queue locally and resume when an approved route becomes reachable.
Service behavior
Local operation and connectivity
Across a route
- Delivery resumes only across explicitly configured and reachable routes.
- Relay does not merge arbitrary records or create a shared mutable database.
Confirmed current integration
Modules with verified service paths
Only module integrations confirmed in the current implementation are listed here. Planned packaging, architectural relationships, and unverified paths are excluded.
Deployment placement
Where it fits
Baseline deployment
Barangay node; Local command node; Designated support node
Hardware, power, connectivity, training, travel, and field logistics remain deployment-specific.Operations and security
Boundaries operators must preserve
Operational considerations
- Monitor queue age, quarantine, attempts, and destination health.
- Set retention and replay policy per message contract and deployment topology.
Security boundary
- Authenticate producers, destinations, and operational webhook consumers.
- Minimize envelope content and avoid treating transport acceptance as business acceptance.
Practical questions
Frequently asked questions
Does Relay synchronize every PBB database?
No. Relay sends only selected, approved messages. It does not copy entire databases or automatically combine records from different nodes.
What happens when the destination is unreachable?
Relay can keep an accepted message on the local node and try again later, following the delivery and storage rules set for that deployment.
Who owns the meaning of a Relay message?
The apps sending and receiving the message must agree on what it means, what information is allowed, who may use it, how duplicates are handled, and what action should follow.
Can Relay send through any available internet route?
No. Deployment owners must approve where messages may go, how Relay connects, which credentials it uses, and which kinds of messages it may send.
What should operators monitor?
Operators should watch how long messages are waiting, repeated delivery attempts, rejected messages, the health of receiving services, storage limits, and confirmation that messages were acted on.
Status and readiness
Integrated
Store-and-forward envelopes, retry handling, delivery state, and selected module integrations are implemented.
Remaining hardening work
- Finalize topology-specific token ownership and rotation.
- Publish retention, retry, quarantine, and recovery runbooks.
- Load-test each approved route and message contract before field rollout.
Companion services
Related infrastructure
Broader platform context
Architecturally related modules
These relationships provide context and do not assert a confirmed current service integration. Verified integration paths appear in the earlier confirmed-integration list.
Briefing and pilot discussion
Discuss PBB Relay in a local PBB deployment
Explore how a local-node deployment could support practical service continuity in your community.