cijber/servitor
2
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
No description
1 commit 1 branch 0 tags 384 KiB
Kotlin 100%
Find a file
eater e4b0e720fa
Initial commit
2020-01-27 22:09:29 +01:00
blobs Initial commit 2020-01-27 22:09:29 +01:00
common Initial commit 2020-01-27 22:09:29 +01:00
engine Initial commit 2020-01-27 22:09:29 +01:00
gateway Initial commit 2020-01-27 22:09:29 +01:00
gradle/wrapper Initial commit 2020-01-27 22:09:29 +01:00
monolith Initial commit 2020-01-27 22:09:29 +01:00
relay Initial commit 2020-01-27 22:09:29 +01:00
.gitignore Initial commit 2020-01-27 22:09:29 +01:00
build.gradle Initial commit 2020-01-27 22:09:29 +01:00
gradle.properties Initial commit 2020-01-27 22:09:29 +01:00
gradlew Initial commit 2020-01-27 22:09:29 +01:00
gradlew.bat Initial commit 2020-01-27 22:09:29 +01:00
README.md Initial commit 2020-01-27 22:09:29 +01:00
settings.gradle Initial commit 2020-01-27 22:09:29 +01:00

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).