Add example using tags and topics
@kmoralesml is already working on this.
Since Oct 1, 2021.
Assessment
This issue has not been assessed yet.
Description
It would be great to have an example that shows a good use case for tags and topics.
Tags: used as a way to indicate to other members of the network how to process the message. For example, is this a new customer order, or is someone cancelling an order?
Topic: used to ensure related messages are processed sequentially in order. For example, all messages related to a certain customer ID may be put on the same topic. This ensures that everything that customer is doing happens in order, and it also means that specific customer's messages will not block another customer's messages.
- Dominant language
- TypeScript
- Stars
- 25
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-firefly/samples
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hyperledger-firefly/samples#20 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
hyperledger-firefly/samples#36 · 2 reactions ·
-
Add request/response exampleMay be free again @apurvaaa claimed this 1845 days ago, and no pull request is open. Opengood first issue
hyperledger-firefly/samples#17 · 1 comment · 1 assignee ·
-
Add webhooks exampleMay be free again @scaraclette claimed this 1845 days ago, and no pull request is open. Opengood first issue
hyperledger-firefly/samples#16 · 1 comment · 1 assignee ·
All issues in hyperledger-firefly/samples
Similar issues
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ranxianglei/billion-context#4172 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
awslabs/threat-composer#362 ·
Maintainers usually reply within 1 day
-
Area/Cloud Needs Triage Type/Bug
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
wso2/product-integrator#2847 ·
Maintainers usually reply within 1 day