KubeMQ Reviews

Oz and Lior provided support in less than one working day. Quick and helpful! The Software is great as well!

Not much to dislike about KubeMQ, it handles all our needs effectively.

The quickest way to get started is to use their deployment tool or to contact their Support team!

We use KubeMQ as a messaging service between our microservices. Unlike other services which provide message passing, KubeMQ supports pub/sub, event queueing as well as RPC. It is better to use rather than having multiple messaging systems that require setting up custom metric servers.

Its hybrid cloud messaging service and integration of Microservices.

Its little difficult to configure compared to other mqs

It helps me to communicate with my Microservices hosted in Kubernetes cluster.

KubeMQ use really small sources of CPU and Memory to collect big data of message comes example from ad internet. If somebody working with big traffic and don't want use really big resource of CPU or Memory something like 8 CPU and 64 GB RAM should change the message broker on Native KubeMQ

At the moment, there are no flaws in the KubeMQ software, it is a young software and it may not convince everyone to this product, but this is what you now need, something that is light and efficient and at the same time not complicated to use and that is what KubeMQ is.

Anybody who need light and efficiency message broker should migrate to KubeMQ native message broker into Kubernetes

We can build small kubernetes cluster and collect big traffic.

Due to its flexibility, computational cost and documentation, it is simple and practical.

And the coolest is done in Go

I still haven't found something that I didn't like, for example I use RabbitMQ and Kafkae and I was able to easily do what they do with more complexity and in kubeMQ it is as if I had demystified everything, everything was simpler and more practical, I loved it.

The tool being native k8s and consumed as little hardware as possible in line with its flexibility and practicality, it is difficult not to use it and put it into production on a daily basis.

KubeMQ is a fantastic replacement of services like AWS SQS, SNS, Lambda, API Gateway when you are looking to have portability between cloud environments/on-premise deployments. It provides an excellent, rich feature set that provides K8s native applications with a wide range of event-driven options available to within the cluster.

Ease-of-use in deployment - they make it really quite simple to get up and running for a variety of use-cases. With new tools like Bridges and Targets, they are even extending far more advanced multi-cloud/multi-deployment options that allow developers/engineers a wide range of possibilities for event-driven systems.

KubeMQ supports a number of popular communication patterns (Pub/Sub, sending events, event sourcing, even CQRS commands and queries). It has client libraries for programming languages I use (C# and Go) and the ability to use REST API. It also provides a dashboard to monitor activity.

No tracing support in the C# client library. Also, I was not able to connect the dashboard in my Kubernetes cluster (though locally it worked fine).

I use KubeMQ for communication between microservices. With KubeMQ I am able to have some microservices working as BFF (Backend For Frontend. BFF microservices provide API for my applications, they take care of user authorization and authentication and other stuff like this. On the other hand, some services are left fully internal, they do a real job and react and commands, queries, and events from BFF services.

Cross languages

Kubernetes native

Versatility

Does not support python 2.7

KubeMQ is a modern message queue and message broker that was specifically developed to work in Kubernetes environment. As such, when deploying with Kubernetes, it is very easy to use and it provides superior performance. KubeMQ is working smoothly and transparently with Kubernetes to provide scalable, high available and secured applications.

There is a limited variety of connectors and bridges available today for KubeMQ, but I found their technical support very attentive and ready to address our proprietary design needs.

If you develop or migrate to Kubernetes environment, it is highly recommended to consider KubeMQ. As it supports all messaging patterns such as Queue, Stream, Pub/Sub and RPC it is most likely to address your use cases, all by a single solution.

There is a substantial need for messaging and queuing in our microservices architecture that KubeMQ solves. It runs easily with Kubernetes and connect natively to the cloud-native ecosystem.

KubeMQ allows me to use message queues, PubSub, and RPC all in one microservice, this means that I don't have to train my team on 3 different services I can just train them how to use this singular microservice.

Their NodeJS SDKs code is quite hard to follow and doesn't have support for TypeScript, although this can be easily bridged as KubeMQ just uses GRPC and Rest.

KubeMQ allows me to utilize different types of communication between apps that I wouldn't be able to use otherwise because the hosting of microservices would be too much.

lightweight 30 mb binary(especially comparing to Kafka), easy to install, feat well with service mesh( in my case it was linkerd), grpc interface from the box

Release cycle in helm repository. You should take more attention to versioning in this app.

Problem: 1) new version was come up in helm repo, old was isn't available. I had this case few mounts ago where I've pinned to specific Chart version in requirements.

2) tag latest in helm source code. https://github.com/kubemq-io/charts/blob/master/kubemq/crds/operator.yaml#L19 , it definitely can be considered not as best practices