This repository was archived by the owner on Jan 27, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Pub-Sub API for Indy Read Replica #29
Copy link
Copy link
Open
Labels
Complexity: highLikely to be difficult to implement with several unknowns.Likely to be difficult to implement with several unknowns.Priority: midFeature request is a important to our roadmap but can be delayedFeature request is a important to our roadmap but can be delayed
Description
This is related to #27
There are two reasonable approaches to implementing this.
- WebSockets: WebSockets provide a real-time, two-way communication channel ideal for pub-sub
APIs. Read Replicas can be notified of new transactions which they can then request from the Ledger
or the Ledger can publish transactions to the read replicas as they become available. - RESTful API with Queues: this approach utilizes a message queue to buffer messages and
handle asynchronous delivery to subscribers(in our case a read replica). They are very reliable and
would ensure that every Read Replica is are kept Update to date with new transactions whenever a
connection can be established with them.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: highLikely to be difficult to implement with several unknowns.Likely to be difficult to implement with several unknowns.Priority: midFeature request is a important to our roadmap but can be delayedFeature request is a important to our roadmap but can be delayed