-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
33 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,33 @@ | ||
# rekuest server | ||
# Rekuest | ||
|
||
[![Maintenance](https://img.shields.io/badge/Maintained%3F-yes-green.svg)](https://github.com/arkitektio/rekuest-server/) | ||
![Maintainer](https://img.shields.io/badge/maintainer-jhnnsrs-blue) | ||
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black) | ||
|
||
|
||
Rekuest is one of the core services of Arkitekt. It represents a central repository of | ||
all the connected apps and their provided functionality, their [Nodes](https://arkitekt.live/docs/terminology/nodes). | ||
It also provides ways of interacting with the apps, by providing a central access point, that | ||
apps and users can assign tasks to. Rekuest then takes care of routing the requests to the | ||
appropriate app, which executres the task and returns the result to rekuest, which in turn routes it back | ||
to the caller. Similar to all other Arkitekt ervices, Rekuest exposes a GraphQL API, that can be used to interact with it. | ||
You can find the interactive documentation for the API [here](https://arkitekt.live/explorer). | ||
|
||
## Rekuest Design | ||
|
||
Rekuest itself is designed as a stateless service (in order to be able to scale horizontally), and | ||
interfaces with proven open-source technologies, such as [Redis](https://redis.io/) and [RabbitMQ](https://www.rabbitmq.com/). | ||
to route tasks to the appropriate apps. The following diagram shows the high-level design of Rekuest: | ||
|
||
![Rekuest Design](./docs/schema.png) | ||
|
||
## Developmental Notices | ||
|
||
Rekuest is currently being rewritten to support other message brokers, such as [Kafka](https://kafka.apache.org/). This will | ||
however remain an opt-in feature, and RabbitMQ will remain the default message broker. To learn more about this design decision, | ||
please refer to the [Why Not?](https://arkitekt.live/docs/design/why-not) section. | ||
|
||
You can find the current developmental node of Rekuest [here](https://github.com/arkitektio/rekuest-server-next) | ||
Efforts from this new repository will be merged into this repository once the new version is ready for production. | ||
|
||
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.