Need an illustrative example for triggering ELSA workflow from a client application

I understand from the [documentation](https://v2.elsaworkflows.io/docs/hosting/distributed-hosting) on configuration needed for multi-node setup. But there is no guide or documentation on how to trigger the workflow from outside of ELSA application. My need to host and scale ELSA server independently and not mince and mix it with my business API, which I would prefer to deploy and scale independently. Given this I would like to understand how to trigger an ELSA workflow from the business API, for a distributed hosting model of ELSA.

I understand from other github issues where you can indicated to achieve this via LB on ELSA server (OR) via QueuingWorkflowDispatcher.

Using LB endpoint poses a constraint to always start a workflow with HTTPEndpoint activity to be able to use this approach. Also needs an LB (additional service) for this setup to work.

Using the QueuingWorkflowDispatcher as you had indicated in the other github issue, seems a better approach, but there is no documentation / illustrative code / guide demonstrating usage. It would great if you could help with this, without which I'm stuck in moving forward.