Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create BBEs for new worker related changes #8856

Open
lochana-chathura opened this issue Apr 3, 2024 · 2 comments
Open

Create BBEs for new worker related changes #8856

lochana-chathura opened this issue Apr 3, 2024 · 2 comments
Assignees
Labels
Area/BBE Issues related to BBEs. Category/Content All written content related issues (Technical content, english language etc) Type/Task Tasks to be carried out for the website.

Comments

@lochana-chathura
Copy link
Member

lochana-chathura commented Apr 3, 2024

Description

$subject.

Need to add BBEs for,

  • alternate-receive-action
  • multiple-receive-action
  • conditional-send
  • named-worker-decl with on-fail-clause
@lochana-chathura lochana-chathura added Type/Task Tasks to be carried out for the website. Area/BBE Issues related to BBEs. Category/Content All written content related issues (Technical content, english language etc) labels Apr 3, 2024
@lochana-chathura
Copy link
Member Author

We need to arrange the new BBEs in the right order allowing the users to follow them sequentially.

I would suggest the below order.

Concurrency:

  1. Asynchronous function calls
  2. Named workers
  3. Sequence diagrams
  4. Wait for workers
  5. Strands
  6. Named worker return values
  7. Alternate wait
  8. Multiple wait
  9. Named workers and futures
  10. Inter-worker message passing
  11. Inter-worker failure propagation
  12. Named worker with on fail clause
  13. Synchronize message passing
  14. Asynchronize message passing
  15. Flush
  16. Alternate receive
  17. Multiple receive
  18. Conditional send (Since we are using 16 and 17 in the 18 BBE example this has to come last)

@lochana-chathura
Copy link
Member Author

It turned out Named worker with on-fail-clause depends on alternate-receive. (https://github.com/ballerina-platform/ballerina-distribution/pull/5296/files#r1557228582)

I would propose following new order.

  1. Asynchronous function calls
  2. Named workers
  3. Sequence diagrams
  4. Wait for workers
  5. Strands
  6. Named worker return values
  7. Alternate wait
  8. Multiple wait
  9. Named workers and futures
  10. Inter-worker message passing
  11. Alternate receive
  12. Multiple receive
  13. Conditional send (we are using 11/12 here)
  14. Inter-worker failure propagation
  15. Named worker with on fail clause (we are using 11/12 here)
  16. Synchronize message passing
  17. Asynchronize message passing
  18. Flush

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/BBE Issues related to BBEs. Category/Content All written content related issues (Technical content, english language etc) Type/Task Tasks to be carried out for the website.
Projects
Status: PR Sent
Development

No branches or pull requests

2 participants