System Architecture with Dotnet SDK

Jakenuts
Sat, 13 Jul 2024 18:08:13 +0000
Community Support

All the examples I’ve found using the dotnet SDK reference the workflow (and activities) in both the workers and the client code that initiates new workflows.

I was under the impression that you could build a decoupled system where one system could start a workflow without caring where/how it would be executed eliminating other decoupling methods like SQS and direct api calls. Since I seem to need the full binary logic of the workflow to exist in every place that might call it that feels pretty coupled. Am I misunderstanding the options or is there a way to execute a workflow by name and some contract for parameters.

Thanks!

3 posts - 2 participants