Nexus Decision Guide FAQs

Question 1

Is Nexus suitable for simple external API calls?

Accepted Answer

No, that is considered an anti-pattern. If you only need to call an HTTP API without cross-namespace durability requirements, a regular Temporal Activity is more efficient.

Question 2

How does Nexus help with team independence?

Accepted Answer

Nexus provides clean service contracts and allows teams to maintain separate namespaces, workers, and deployment cycles while maintaining durable communication.

Question 3

When should I use Nexus instead of Child Workflows?

Accepted Answer

Use Nexus only when you need durable communication across different Temporal namespaces. If your workflows are in the same namespace, Child Workflows provide the same decomposition with much less overhead.

Question 4

What factors contribute to the Nexus complexity score?

Accepted Answer

The complexity score evaluates the number of consuming namespaces, the complexity of handler operations (sync vs async), team independence requirements, and your existing namespace topology.

Question 5

Does this skill provide code for implementing Nexus?

Accepted Answer

No, this skill is focused on the architectural decision-making framework. For implementation details and code examples, you should use the nexus-operations skill.

Nexus Decision Guide

Key Features

Use Cases

Nexus Decision Guide

Key Features

Use Cases