Skip to content

Add Nexus adoption decision tree to evaluate nexus page #4123

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.

Sign up for GitHub

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

Open
jsundai wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Nexus adoption decision tree to evaluate nexus page #4123

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/evaluate/development-production-features/temporal-nexus.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,14 @@ Nexus supports cross-team, cross-domain, cross-namespace, multi-region, and mult

Unlike other forms of inter-service communication, Nexus combines a familiar programming model with the resiliency of the Temporal Platform and its queue-based Worker architecture.

Use the following decision tree to help determine if Nexus is right for your use case:

<div style={{textAlign: 'center', margin: '2rem 0'}}>
Copy link
Contributor

@flippedcoder flippedcoder Jan 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about making this a component? We could definitely reuse this!

Copy link
Contributor

@flippedcoder flippedcoder Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just fyi, I went ahead and made this a component in one of my PRs because it was really useful!

<a href="/diagrams/nexusadoptiontree.png" target="_blank">
<img src="/diagrams/nexusadoptiontree.png" alt="Should I use Nexus? Decision tree" style={{maxWidth: '100%', cursor: 'pointer'}} />
</a>
</div>

### Benefits

- **Integrated Temporal experience** \- with improved security, observability, and reliability.
Expand Down
Binary file added static/diagrams/nexusadoptiontree.png
View file
Open in desktop
Copy link
Contributor

@flippedcoder flippedcoder Jan 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple comments on the image:

  • Does namespaces need to be capitalized to match other parts of the docs?
  • I don't quite understand what Is cross-x support is a future goal and not time critical? means? Could this be rephrased?

Copy link
Contributor

@lennessyy lennessyy Jan 23, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think we should use excalifont -- they are hard to read and not super accessible. do we have a style guide for diagrams? we should make one if we don't to make sure they are consistent across the site

this diagram is already complex, so i think we should opt for cleaner fonts

Copy link
Contributor Author

@jsundai jsundai Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I agree. I put in a request to design about it awhile ago especially for a light/dark mode version.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.