Skip to content

Latest commit

 

History

History
89 lines (66 loc) · 2.18 KB

README.md

File metadata and controls

89 lines (66 loc) · 2.18 KB

Tabour Core

Concept

Tabour follows a modular architecture and the core concept of it's architecture is a Registry

You need to register the registry to the Tabour container and start the Tabour container. After that step, the consumers that you have configured and registered will start consuming messages from the queues they have been configured to consume.

Registry

A registry is a collection of Consumers and Producers for a specific messaging system. Tabour comes with a handful of functions that create consumers and producers which you need to attach (register) to a specific registry

Available registries

Consumer

A consumer is a class that has been configured to consume messages from a specific queue/topic depending on the messaging system.

Available consumers

Producer

A producer is a class that has been configured to produce messages to a specific queue/topic depending on the messaging system.

Available consumers

Creating a tabour instance

val container = tabour { numOfThreads = 2 }

Registering registries to the tabour instance

// check docs/sqs/registry.md about the creation of a registry
container.register(registry)

starting tabour

tabour.start()

Installation

Build toolInstruction
Maven
<dependency>
    <groupId>com.katanox.tabour</groupId>
    <artifactId>core</artifactId>
    <version>{version}</version>
</dependency>
Gradle Groovy DSL
implementation 'com.katanox.tabour:core:{version}'
Gradle Kotlin DSL
implementation("com.katanox.tabour:core:{version}")
Scala SBT
libraryDependencies += "com.katanox.tabour" % "core" % "{version}"