Concepts

redpesk Distribution Variants

There are 2 variants for the main redpesk distribution:

  • LTS version:
    • full name: redpesk LTS batz 2.0
    • aligned on RedHat 9.2 for Long Term Support, this is used for industrial and commercial needs
    • short name: rpbatz
  • LTS update version:
    • full name: redpesk LTS batz 2.0-update
    • updated version of redpesk LTS batz 2.0 that provides latest changes (security or bug fixes) on top of batz 2.0
    • short name: rpbatz-update

rp-cli

rp-cli lets the user interact with the redpesk platform just as the redpesk web user interface (UI) does. But when the web UI is a fancy graphical environment, rp-cli is made to be an easy and efficient tool, based on command line.

This is why rp-cli is great to automate every single action that can be done on the web UI. Nevertheless it is also much more. Indeed, for all the command line heroes out there, rp-cli has been designed to be easily manipulated and to be as intuitive as possible thank to its auto-completion.

Furthermore, rp-cli is now able to work together with the local builder in order to:

  • Build and package locally your application (before creating it in the redpesk platform)
  • Build a custom redpesk image locally

It is therefore a great tool when you need a fast iteration process!

Currently rp-cli is available for Linux environments only.

Application Framework Binder

The binder provides the way to connect applications to the services that it needs.

It provides a fast way to securely offer APIs to applications written in any language and running almost anywhere.

  • The binder is developed for redpesk but it is not bound to it.
  • The binder is the usual name.
  • The binary is named afb-binder.
  • The name afb-binder stands for Application Framework Binder.

Each binder is in charge of binding one instance of an application or service to the rest of the system, applications and services.

Within redpesk, the connection between services and applications is automatically set up by the application framework, using the binder.

Interconnection of binders

The framework interprets application manifest files to setup binding configurations of the binders.

interconnection

The previous figure shows that binders are interconnected.

The figure shows 4 several application/service: A, B, C and D.

The application A might use an API that is shown as a local binding but that in reality runs within the context of D.

The application framework of redpesk takes care of making the plumbing working.

Role of binders in micro service architecture

Inside the redpesk micro-service architecture, the binder is used for two main purposes, either together or separately:

  1. Entry point of user applications for using micro-services
  2. Interconnection of services together

Services can be interconnected in the same process, in different processes of the same machine or even over the network on different nodes.