You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 16, 2020. It is now read-only.
ATTENTION: This is the Solo branch of Dispatch. Read the Dispatch
Solo section to understand what that means.
Dispatch is a framework for deploying and managing serverless style applications. The intent is a framework
which enables developers to build applications which are defined by functions which handle business logic and services
which provide all other functionality:
State (Databases)
Messaging/Eventing (Queues)
Ingress (Api-Gateways)
Etc.
Our goal is to provide a substrate which can be built upon and extended to serve as a framework for serverless
applications. Additionally, the framework must provide tools and features which aid the developer in building,
debugging and maintaining their serverless application.
Dispatch Solo
Dispatch Solo is a simplified branch of Dispatch. The objective is to remove as many dependencies as possible
while maintaining functionlity. Dispatch Solo is a single binary which only relies on Docker as dependency,
distributed as an OVA. The trade-off of this simplification is scale and persistence. However, it is the perfect
platform for evaluation and learning.
The diagram below illustrates the different components which make up the Dispatch project:
Installation
The quickest way to deploy Dispatch Solo is using the OVA, following the documentation in the quickstart guide. Alternatively, Dispatch Solo can be built from source by following the instructions below.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull
requests, and do our best to process them as fast as we can. If you wish to contribute code and you have not signed our
contributor license agreement (CLA), our bot will update the issue when you open a Pull
Request. For any questions about the CLA process, please
refer to our FAQ.
Before you start to code, we recommend discussing your plans through a GitHub
issue or discuss it first with the official project
maintainers via the #Dispatch Slack Channel, especially
for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you
feedback on your design, and help you find out if someone else is working on the same thing.