dispatch.test package #86
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's difficult for users to test their Dispatch endpoint. To dispatch calls to functions, users must connect to the production Dispatch orchestrator, and also jump through hoops to expose their local endpoint on the internet (e.g. using ngrok) so that Dispatch can access it.
This PR improves and exports the internal classes we were using to test the SDK. The new
dispatch.test
package contains a fully functional (albeit very simple) local Dispatch service that can be used in place of the production Dispatch orchestrator. This allows users to play around with the basic functionality of Dispatch, and unit/integration test their functions/graphs, all without requiring an internet connection.The provided Dispatch service does the absolute bare minimum to drive a graph of execution to completion. Internally, it uses a simple FIFO queue. There are no limits and no adaptive concurrency control.