DISID is a strategic KubeMQ partner with experienced devops and developers in the KubeMQ ecosystem.

KubeMQ is a native messaging broker for Kubernetes, enabling continuous data processing. As soon as this data is available, it is processed sequentially, through channels that allow the ingestion of infinite data flows without time limits.

In the Digital Transformation projects developed by DISID, KubeMQ is a key piece for those companies that need to process information in real time and from multiple data sources. KubeMQ integrates with numerous technologies, thus allowing to build real-time data flows between different systems and applications in a decoupled way. In addition, with low latency, high availability and horizontal scalability, it can absorb any peak load.

KubeMQ characteristics

Kubernetes Native

Designed to install on Kubernetes. Kubernetes installation, cluster management and maintenance tasks are extremely agile. In Digital Transformation processes this feature is extremely important as it allows the team to focus on the business objectives of the companies and avoid spending time and money on tasks that do not add business value.


Deployed as Statefulset cluster in less than 1 minute

  • Blazing fast (written in Go)
  • Small and lightweight Docker container (30MB)
  • Scales instantly
  • With or without Persisted Volume
  • All nodes are active and serve traffic
  • Observability support: Prometheus, Jeager, Zipkin, AWS X-Ray, Datadog, Google Stack, Driver, HoneyComb

Ease of use

  • Less than 1 minute to deploy
  • Full Dynamic Routing methodology require only channel name to send a message (Eliminate the hassle of developers and DevOps to define exchanges, brokers, channels, routes and predefined topics)
  • Transparent upgrade from a dev environment to a production environment
  • KubeMQctl, Simple to use CLI tool to deploy, monitor and use KubeMQ

All messaging patterns included

  • Asynchronous and Synchronous messaging with support for guaranteed message delivery, At Most Once Delivery and At Least Once Delivery models
  • Supports durable FIFO based Queue, Publish-Subscribe Events, Publish-Subscribe with Persistence (Events Store), RPC Command and Query messaging patterns
  • Supports gRPC, Rest and WebSocket Transport protocols with TLS support

KubeMQ scalable architecture

The connector-based architecture model allows extending KubeMQ’s core functionalities in an easy, non-intrusive way and with minimal development effort.

KubeMQ includes a set of default connectors (Out-Of-The-Box) that allow to instantly connect microservices with external services, with legacy platforms and with a wide number of systems.

The main connectors are: KubeMQ Bridges, KubeMQ Targets and KubeMQ Sources.


KubeMQ Bridges

KubeMQ Bridges allows you to replicate, aggregate and transform messages between KubeMQ clusters no matter where they are located, enabling you to build true cloud-native messaging for a hybrid cloud.

KubeMQ Targets

KubeMQ Targets connects external systems and cloud services with KubeMQ. See the list of supported external systems and services here.

KubeMQ Sources

KubeMQ Sources allows KubeMQ to receive data from external systems such as RabbitMQ, Kafka, MQTT and REST APIs. Thanks to this connector, it is extremely agile to migrate from legacy systems to microservices architectures on top of Kubernetes. See the list of supported external systems here.

Comparison of KubeMQ with Kafka and others

Comparison of KubeMQ with Kafka, RabbitMQ, Amazon SQS and Redis Pub/Sub.

KubeMQ: Plataforma de mensajería Kubernetes

KubeMQ Services:

Analysis and design

Design of solutions that need to process information in real time to add value to our clients’ business.

Configuration and commissioning

Technical assistance, installation, customization, configuration, maintenance and support.