📄️ Overview & Introduction
The Messaging Services is implemented as a Publish/Subscribe Service. Instead of focusing on a single Messaging API specification for handling the logic of publishing/subscribing to the broker network the API focuses on creating nodes of Publishers and Subscribers as a Service.
📄️ Using Apache Kafka as a Backend Message system
The ARGO Messaging API has been designed to rely on a generic Message Back-end Interface and use specific implementation of that interface for supporting different systems. Right now the first implementation for the messaging back-end relies on Apache Kafka as a distributed messaging system.
📄️ Data flow in Argo Messaging
The main steps of the messaging API:
📄️ Authentication & Authorization
Authentication is the process of determining the identity of a client, which is typically a user account. Authorization is the process of determining what permissions an authenticated identity has on a set of specified resources. In the Messaging API, there can be no authorization without authentication.
📄️ Initial Project & User Management
This document describes some of the more advanced setup you may need to do while configuring and deploying the ARGO Messaging Service.