Skip to content

Commit 24cf29d

Browse files
committed
Sync working groups
1 parent 91edc34 commit 24cf29d

File tree

1 file changed

+45
-45
lines changed

1 file changed

+45
-45
lines changed

_data/wg.yaml

Lines changed: 45 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,50 @@
11
---
22
working-groups:
3+
- title: "Unified Saga implementation"
4+
board-url: "https://github.com/orgs/quarkusio/projects/48"
5+
short-description: |
6+
The main objective of this working group is to unify Quarkus's story about Saga-based transactions.
7+
readme: |
8+
<h3>Objective:</h3>
9+
<p>The main objective of this working group is to unify Quarkus's story about Saga-based transactions.</p>
10+
<h3>The Problem</h3>
11+
<p>The primary saga solution for distributed transactions is <a href="https://github.com/quarkusio/quarkus/tree/main/extensions/narayana-lra">narayana-lra</a> extension. However, it wasn't maintained and marketed as the number one solution for distributed sagas. So we either need to update LRA to make a unified solution for Quarkus or pick a different solution that was introduced in the meantime. This WG will unify Quarkus's story in a distributed transaction solution.</p>
12+
<h3>The proposed Solution</h3>
13+
<p>We will investigate and compare available solutions for the saga-based implementation of the distributed tx processing. This will be documented, and the choice should be proven to be able to drive development and innovation in this area. We will ensure the solution meets the Quarkus standards (build/runtime split, dev service, dev ui).</p>
14+
<h3>Definition of Done</h3>
15+
<ul>
16+
<li>A new guide for the distributed tx (or the chosen solution if there is only one)</li>
17+
<li>Blog post comparing available solutions or just marketing the chosen solution</li>
18+
<li>Quarkus insights about this topic</li>
19+
</ul>
20+
<h3>Scope of Work</h3>
21+
<p>The scope of this WG is to pick a chosen saga-based implementation and make it Quarkus native (dev mode, any possible enhancements). We will choose implementation with an already available Quarkus integration. Research of new saga-based alternatives is out of scope.</p>
22+
<h3>Organizing the Work</h3>
23+
<p>Communication and Transparency:</p>
24+
<p>Coordination will be done in this GitHub discussion and the individual GitHub issues. GitHub issues can be closed if the saga-solution is not to be updated anymore. The decision of the chosen solution will be stated also as the resolution of https://github.com/quarkusio/quarkus/issues/34181.</p>
25+
<p>This work can take place in either Quarkus core (narayana-lra) or some new extension that will be provided in Quarkiverse.</p>
26+
<h3>Expected Timeline:</h3>
27+
<p>Milestone 1 - Document in this discussion saga-based implementations alternatives
28+
Milestone 2 - Pick one solution that will be Quarkus Saga solution
29+
Milestone 3 - Update the chosen alternative for Quarkus standards (simplification of use, dev * features)
30+
Milestone 4 - Create a guide to document it
31+
Milestone 5 - Blog + Quarkus insights</p>
32+
<hr />
33+
<ul>
34+
<li>Point of contact: @xstefank (@<strong>Martin Stefanko|448453</strong> on Zulip)</li>
35+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/46672</li>
36+
<li>Deliverable: TBD</li>
37+
</ul>
38+
status: on track
39+
lts: false
40+
completed: false
41+
last-activity: 2025-07-24
42+
last-update-date: 2025-07-24
43+
last-update: |
44+
Milestone 1 - Document in this discussion saga-based implementations alternatives -- DONE
45+
deliverable: TBD
46+
point-of-contact: "@xstefank (@<strong>Martin Stefanko|448453</strong> on Zulip)"
47+
proposal: https://github.com/quarkusio/quarkus/discussions/46672
348
- title: "Offering Metadata and Tooling Integration"
449
board-url: "https://github.com/orgs/quarkusio/projects/52"
550
short-description: |
@@ -451,51 +496,6 @@ working-groups:
451496
last-update-date: 2025-04-01
452497
last-update: |
453498
In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release.
454-
- title: "Unified Saga implementation"
455-
board-url: "https://github.com/orgs/quarkusio/projects/48"
456-
short-description: |
457-
The main objective of this working group is to unify Quarkus's story about Saga-based transactions.
458-
readme: |
459-
<h3>Objective:</h3>
460-
<p>The main objective of this working group is to unify Quarkus's story about Saga-based transactions.</p>
461-
<h3>The Problem</h3>
462-
<p>The primary saga solution for distributed transactions is <a href="https://github.com/quarkusio/quarkus/tree/main/extensions/narayana-lra">narayana-lra</a> extension. However, it wasn't maintained and marketed as the number one solution for distributed sagas. So we either need to update LRA to make a unified solution for Quarkus or pick a different solution that was introduced in the meantime. This WG will unify Quarkus's story in a distributed transaction solution.</p>
463-
<h3>The proposed Solution</h3>
464-
<p>We will investigate and compare available solutions for the saga-based implementation of the distributed tx processing. This will be documented, and the choice should be proven to be able to drive development and innovation in this area. We will ensure the solution meets the Quarkus standards (build/runtime split, dev service, dev ui).</p>
465-
<h3>Definition of Done</h3>
466-
<ul>
467-
<li>A new guide for the distributed tx (or the chosen solution if there is only one)</li>
468-
<li>Blog post comparing available solutions or just marketing the chosen solution</li>
469-
<li>Quarkus insights about this topic</li>
470-
</ul>
471-
<h3>Scope of Work</h3>
472-
<p>The scope of this WG is to pick a chosen saga-based implementation and make it Quarkus native (dev mode, any possible enhancements). We will choose implementation with an already available Quarkus integration. Research of new saga-based alternatives is out of scope.</p>
473-
<h3>Organizing the Work</h3>
474-
<p>Communication and Transparency:</p>
475-
<p>Coordination will be done in this GitHub discussion and the individual GitHub issues. GitHub issues can be closed if the saga-solution is not to be updated anymore. The decision of the chosen solution will be stated also as the resolution of https://github.com/quarkusio/quarkus/issues/34181.</p>
476-
<p>This work can take place in either Quarkus core (narayana-lra) or some new extension that will be provided in Quarkiverse.</p>
477-
<h3>Expected Timeline:</h3>
478-
<p>Milestone 1 - Document in this discussion saga-based implementations alternatives
479-
Milestone 2 - Pick one solution that will be Quarkus Saga solution
480-
Milestone 3 - Update the chosen alternative for Quarkus standards (simplification of use, dev * features)
481-
Milestone 4 - Create a guide to document it
482-
Milestone 5 - Blog + Quarkus insights</p>
483-
<hr />
484-
<ul>
485-
<li>Point of contact: @xstefank (@<strong>Martin Stefanko|448453</strong> on Zulip)</li>
486-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/46672</li>
487-
<li>Deliverable: TBD</li>
488-
</ul>
489-
status: on track
490-
lts: false
491-
completed: false
492-
last-activity: 2025-04-08
493-
last-update-date: 2025-07-24
494-
last-update: |
495-
Milestone 1 - Document in this discussion saga-based implementations alternatives -- DONE
496-
deliverable: TBD
497-
point-of-contact: "@xstefank (@<strong>Martin Stefanko|448453</strong> on Zulip)"
498-
proposal: https://github.com/quarkusio/quarkus/discussions/46672
499499
- title: "Roq :: Quarkus SSG"
500500
board-url: "https://github.com/orgs/quarkiverse/projects/6"
501501
short-description: |

0 commit comments

Comments
 (0)