All Projects → dbmqproject → dbmq

dbmqproject / dbmq

Licence: GPL-3.0 License
Docker-based Message Queuing

Programming Languages

python
139335 projects - #7 most used programming language
Dockerfile
14818 projects

Projects that are alternatives of or similar to dbmq

Kombu
Kombu is a messaging library for Python.
Stars: ✭ 2,263 (+5702.56%)
Mutual labels:  message-queue, celery
celery.node
Celery task queue client/worker for nodejs
Stars: ✭ 164 (+320.51%)
Mutual labels:  worker, celery
Vernemq
A distributed MQTT message broker based on Erlang/OTP. Built for high quality & Industrial use cases.
Stars: ✭ 2,628 (+6638.46%)
Mutual labels:  message-queue, broker
Pmq
信也科技MQ消息系统
Stars: ✭ 333 (+753.85%)
Mutual labels:  message-queue, broker
aioconnectors
Simple secure asynchronous message queue
Stars: ✭ 17 (-56.41%)
Mutual labels:  message-queue, broker
Xxl Mq
A lightweight distributed message queue framework.(分布式消息队列XXL-MQ)
Stars: ✭ 358 (+817.95%)
Mutual labels:  message-queue, broker
Ytask
YTask is an asynchronous task queue for handling distributed jobs in golang(go异步任务框架)
Stars: ✭ 121 (+210.26%)
Mutual labels:  worker, celery
Autoops
linux资产管理,cmdb,django, webssh,运维管理平台,数据库操作平台 本项目已停止开发!因长时间未对代码进行维护,可能会造成项目在不同环境上无法部署、运行BUG等问题,请知晓!项目仅供参考!
Stars: ✭ 340 (+771.79%)
Mutual labels:  tornado, celery
leek
Celery Tasks Monitoring Tool
Stars: ✭ 77 (+97.44%)
Mutual labels:  worker, celery
rabbitmq-labs
The source code for my RabbitMQ tutorials.
Stars: ✭ 45 (+15.38%)
Mutual labels:  worker, message-queue
Bugsnag Python
Official bugsnag error monitoring and error reporting for django, flask, tornado and other python apps.
Stars: ✭ 69 (+76.92%)
Mutual labels:  tornado, celery
wave
MQTT Broker - for IoT, DIY, pubsub applications and more
Stars: ✭ 24 (-38.46%)
Mutual labels:  message-queue, broker
Tornado Celery
Non-blocking Celery client for Tornado
Stars: ✭ 561 (+1338.46%)
Mutual labels:  tornado, celery
Message Bus
Go simple async message bus
Stars: ✭ 166 (+325.64%)
Mutual labels:  message-queue, broker
Webspider
在线地址: http://119.23.223.90:8000
Stars: ✭ 340 (+771.79%)
Mutual labels:  tornado, celery
Immuni Backend App Configuration
Repository for the backend app configuration
Stars: ✭ 33 (-15.38%)
Mutual labels:  webserver, celery
logtoes
Demo of Asynchronous pattern (worker) using Python Flask & Celery
Stars: ✭ 49 (+25.64%)
Mutual labels:  worker, celery
Online-Judge
Online Judge for hosting coding competitions inside NIT Durgapur made by GNU/Linux Users' Group!
Stars: ✭ 19 (-51.28%)
Mutual labels:  broker, celery
fastweb
fastweb is a web-server integration solution. It based on tornado, celery, thrift.
Stars: ✭ 17 (-56.41%)
Mutual labels:  tornado, celery
gmqtt
Golang MQTT Broker.
Stars: ✭ 75 (+92.31%)
Mutual labels:  broker


Docker-based Message Queuing
Docker SDK - Article on Medium - Read the Docs here ➤
Build and ship your Dockerized Django applications and feel free to use MBs

Documentation Status

Introduction

Docker-based Message Queuing (DBMQ) is an efficient way to run the pre-built configurations on the build process of Dockerfiles. Once you have finished configuring, you will be able to create your images based on your configurations. DBMQ is very flexible with Django projects and you might stay away from troubles with creating a Dockerized Django project. After the building process, your image will be ready to get started. Use a text editor to step through your container and make changes. (the pre-installed editor is Vim)

Why DBMQ is Needed?

This system locates between the user and the Docker service. You config your requirements and let this automated system to provide them to you. You don't need to be a genius in Docker, just keep configuring. There is a channel between Docker and DBMQ called SDK. There are several services, but there is only one service that allows DBMQ to interact with Docker, which called Docker Engine API. Docker is a distributed computing platform that allows you to decrease the latency and to cheap your project. You can keep up your project with distributed resources. (brokers, databases, etc)

Installation

Before you clone DBMQ, you better make sure your Docker service is installed successfully. If there is something wrong, you can start browsing on the Docker Installation Guide on Linux. Make sure your Docker is running.

$ sudo systemctl status docker
● docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor p>
     Active: active (running) since Mon 2020-09-07 23:47:00 +0430; 1s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 5644 (dockerd)
      Tasks: 25 (limit: 4502)
     Memory: 184.1M
     CGroup: /system.slice/docker.service
             ├─5644 /usr/bin/dockerd -H fd://
             └─5652 containerd --config /var/run/docker/containerd/containerd.t>

Clone the repository with the following command and either create a new virtualenv or, just keep installing the libraries on your real machine.

$ git clone https://github.com/lnxpy/DBMQ.git
...
$ cd ./DBMQ
$ virtualenv .venv
...
$ source .venv/bin/activate
(.venv)$ pip install -r requirements.txt
  • Without virtualenv
$ pip3 install -r requirements.txt

Installation has been completed. For the further steps, check out the documents.

To-Do

The following to-do task list should be followed in order. If you are experienced enough in these tasks, you can start contributing to DBMQ. Fork the project, create PRs and I'll review them. If you've done any further task, change your task context grammatically in the following list.

  • version 2.1 is being released
  • Docker_images removed from the whole project
  • New logo represented for DBMQ v2.1
  • Start writing documentations (Sphinx)
  • Using python docker images instead of linux distros
  • Tests
  • New feature -> streaming the running containers
  • Updating the links in the exceptions and repo
  • Database implementation process
  • Broker implementation process
  • version 2.2 is being released

License & Contribution

DBMQ is licensed by GPL-v3 (quick guide reference).

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].