Introduction

What is KubeMQ?

Enterprise-grade message broker native for Docker and Kubernetes. Delivered in a production-ready cluster, and designed for any type of workload. KubeMQ is provided as a small, lightweight Docker container, designed for any workload and architecture running in Kubernetes or any other container orchestration system which support Docker.

Main Features

All-batteries included Messaging Broker for Kubernetes environment
Blazing fast (written in Go), small and lightweight Docker container
Asynchronous and Synchronous messaging with support for Exactly One 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 (both RPC and Stream modes)
Runs in Single and cluster modes
No Message broker configuration needed (i.e., queues, exchanges)
Built-in Caching, Metrics, and Tracing
.Net, Java, Python, Go SDKs
Monitoring Dashboard

Kubernetes and Docker Ready

Kubernetes - KubeMQ can be deployed on any Kubernetes cluster as stateful set.
Docker - KubeMQ can run as a single docker container or as high availability cluster.

Messaging Patterns

Queues

KubeMQ supports distributed durable FIFO based queues with the following core features:

Exactly One Delivery - Only one message guarantee will deliver to the subscriber
Single and Batch Messages Send and Receive - Single and multiple messages in one call
RPC and Stream Flows - RPC flow allows an insert and pull messages in one call. Stream flow allows single message consuming in transactional way
Message Policy - Each message can be configured with expiration and delay timers. In addition, each message can specify a dead-letter queue for un-processed messages attempts
Long Polling - Consumers can wait until a message available in the queue to consume
Peak Messages - Consumers can peak into a queue without removing them from the queue
Ack All Queue Messages - Any client can mark all the messages in a queue as discarded and will not be available anymore to consume
Visibility timers - Consumers can pull a message from the queue and set a timer which will cause the message not be visible to other consumers. This timer can be extended as needed.
Resend Messages - Consumers can send back a message they pulled to a new queue or send a modified message to the same queue for further processing.

Pub/Sub

KubeMQ supports Publish-Subscribe (a.k.a Pub/Sub) messages patterns with the following core features:

Event - An asynchronous real-time Pub/Sub pattern.
Event Store -An asynchronous Pub/Sub pattern with persistence.
Grouping - Load balancing of events between subscribers

RPC

KubeMQ supports CQRS based RPC flows with the following core features:

Commands - A synchronous two ways Command pattern for CQRS types of system architecture.
Query - A synchronous two ways Query pattern for CQRS types of system architecture.
Response - An answer for a Query type RPC call
Timeout - Timeout interval is set for each RPC call. Once no response is received within the Timeout interval, RPC call return an error
Grouping - Load balancing of RPC calls between receivers
Caching - RPC response can be cached for future requests without the need to process again by a receiver

Interfaces

gRPC - High performance RPC and streaming framework that can run in any environment, Open source and Cloud Native.
Rest - Restful Api with WebSocket support for bi-directional streaming.

SDK

C# - C# SDK based on gRPC
Java - Java SDK based on gRPC
Go - Go SDK based on gRPC
Python - Python SDK based on gRPC
cURL - cURL SDK based on Rest
Node - Node SDK based on Rest
PHP - PHP SDK based on Rest
Ruby - Ruby SDK based on Rest
jQuery jQuery SDK based Rest

Observability

Metrics - Metrics can be exported to variety of Backend
Tracing - Tracing can be exported to variety of Backend
Backend Support - Prometheus, Honeycomb, AWS X-Ray,Datadog,Jeager,StackDriver,Zipkin

Installation

Every installation method requires a KubeMQ token. Please register to obtain your KubeMQ token.

Docker

Pull and run KubeMQ Docker container:

docker run -d -p 8080:8080 -p 50000:50000 -p 9090:9090 \
-v $PWD:/store -e KUBEMQ_TOKEN=<YOUR_KUBEMQ_TOKEN> kubemq/kubemq

Kubernetes

Run :

kubectl apply -f https://get.kubemq.io/deploy?token=<YOUR_KUBEMQ_TOKEN>

Please refer to our docs for more options.

Get Started

No matter what kind of App or Service you want to build, our three-step checklists will get you set up and ready.

Pick one of the desired message patterns:

Documatation

Visit our Extensive KubeMQ Documentation.

Support

You can reach us at:

ellerbrock / kubemq Goto Github PK

kubemq's Introduction