cijber
/
servitor
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1 Commit
1 Branch
0 Tags
384 KiB
Kotlin 100%
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Go to file
eater e4b0e720fa
Initial commit 		5 years ago
blobs Initial commit 5 years ago
common Initial commit 5 years ago
engine Initial commit 5 years ago
gateway Initial commit 5 years ago
gradle/wrapper Initial commit 5 years ago
monolith Initial commit 5 years ago
relay Initial commit 5 years ago
.gitignore Initial commit 5 years ago
README.md Initial commit 5 years ago
build.gradle Initial commit 5 years ago
gradle.properties Initial commit 5 years ago
gradlew Initial commit 5 years ago
gradlew.bat Initial commit 5 years ago
settings.gradle Initial commit 5 years ago

README.md

Servitor

A workflow engine

Components

This project is split is multiple components which should allow for effective clustering of relevant parts.

Engine

The main component of Servitor, this part executes all logic noted in the workflow files

Relay

The relay component does all the talking to remote endpoints, waits for their answers and puts the result back in the queue for the engine to process

Gateway

The gateway component observes and records all actions happening on the relay and in the engine. It also serves the API (and When Time Comes the web frontend).

Monolith

Monolith is a special version of Servitor, which combines all tech necessary to run Servitor in a single jar. This will be most likely the first thing you'll want to use if you want to play around with Servitor or want to deploy it in a small setup.

Monolith will not require -any- outside dependencies, it will use a bundled software for the message queues (ActiveMQ), key value store (???), and relation database (SQLite).