All Projects → conduitframework → Conduit

conduitframework / Conduit

Licence: mit
A message queue framework, with support for middleware and multiple adapters.

Programming Languages

elixir
2628 projects

Projects that are alternatives of or similar to Conduit

Jafka
a fast and simple distributed publish-subscribe messaging system (mq)
Stars: ✭ 697 (+511.4%)
Mutual labels:  message-queue
Lemon Rabbitmq
乐檬框架之rabbitMQ的解耦实现方式(基于springboot框架),利用ConfirmCallback确保消息安全发送至broker服务器,使用Ack/Nack手动确认消息处理状态,保证broker消息被正确消费
Stars: ✭ 46 (-59.65%)
Mutual labels:  message-queue
Java Notes
📚 计算机科学基础知识、Java开发、后端/服务端、面试相关 📚 computer-science/Java-development/backend/interview
Stars: ✭ 1,284 (+1026.32%)
Mutual labels:  message-queue
Huststore
High-performance Distributed Storage
Stars: ✭ 806 (+607.02%)
Mutual labels:  message-queue
Carmine
Redis client and message queue for Clojure
Stars: ✭ 999 (+776.32%)
Mutual labels:  message-queue
Kubemq
KubeMQ is Enterprise-grade message broker native for Docker and Kubernetes
Stars: ✭ 58 (-49.12%)
Mutual labels:  message-queue
Siberite
Siberite is a simple, lightweight, leveldb backed message queue written in Go.
Stars: ✭ 583 (+411.4%)
Mutual labels:  message-queue
Php Fpm Queue
Use php-fpm as a simple built-in async queue
Stars: ✭ 103 (-9.65%)
Mutual labels:  message-queue
Enqueue Elastica Bundle
The bundle extends functionality of FOSElasticaBundle. Improves performance of fos:elastica:populate command
Stars: ✭ 40 (-64.91%)
Mutual labels:  message-queue
So 5 5
SObjectizer: it's all about in-process message dispatching!
Stars: ✭ 87 (-23.68%)
Mutual labels:  message-queue
Message Queue
第四届阿里中间件性能挑战赛复赛-JAVA-第21名
Stars: ✭ 16 (-85.96%)
Mutual labels:  message-queue
Toro
Multithreaded message processing on Postgres
Stars: ✭ 39 (-65.79%)
Mutual labels:  message-queue
Queuelite.js
Super simple Node.js message queue for fun and prototyping
Stars: ✭ 70 (-38.6%)
Mutual labels:  message-queue
Rmq
Message queue system written in Go and backed by Redis
Stars: ✭ 722 (+533.33%)
Mutual labels:  message-queue
Nats Server
High-Performance server for NATS.io, the cloud and edge native messaging system.
Stars: ✭ 10,223 (+8867.54%)
Mutual labels:  message-queue
Weevent
Event-Driven Architecture Based on Blockchain.基于区块链的事件驱动架构
Stars: ✭ 608 (+433.33%)
Mutual labels:  message-queue
K8s Nats Streaming
NATS Streaming Server on Kubernetes
Stars: ✭ 58 (-49.12%)
Mutual labels:  message-queue
Rsmq
Redis Simple Message Queue
Stars: ✭ 1,556 (+1264.91%)
Mutual labels:  message-queue
Stomp Php
Stomp PHP Client
Stars: ✭ 94 (-17.54%)
Mutual labels:  message-queue
Message Db
Microservice native message and event store for Postgres
Stars: ✭ 1,260 (+1005.26%)
Mutual labels:  message-queue

Conduit

CircleCI Coveralls Hex.pm Hex.pm Hex.pm

A message queue framework, with support for middleware and multiple adapters.

Check out this slide deck for more info.

Installation

The package can be installed as:

  1. Add conduit to your list of dependencies in mix.exs:
def deps do
  [{:conduit, "~> 0.12"}]
end
  1. If you are explicitly stating which applications to start, ensure conduit is started before your application:
def application do
  [applications: [:conduit]]
end

Getting Started

Once conduit is added to your project, you can generate a broker. For example:

mix conduit.gen.broker --adapter amqp
mix conduit.gen.broker --adapter sqs

The Broker is responsible for describing how to setup your message queue routing, defining subscribers, publishers, and pipelines for subscribers and publishers.

See mix help conduit.gen.broker for all the options that are available. For example, specifying the adapter to use.

Officially Supported Adapters

In the future more adapters will be supported.

Configuring the Broker Topology

MQ's have queues which need to be setup and may involve other concepts as well, including exchanges and bindings. Conduit attemps to stay out of the way when you need to define these things because each MQ has a different opinion on what you need.

Because of that, you'll need to looks at the specific adapter for what options are available.

Configuring a Subscriber

A subscriber is responsible for processing messages from a message queue. Typically, you'll have one subscriber per queue. You can generate a subscriber by doing:

mix conduit.gen.subscriber user_created

See mix help conduit.gen.subscriber for all the options that are available.

You can find more information about configuring your subscriber in the adapter specific docs here:

Configuring a Publisher

A publisher is responsible for sending messages. You can find more information abount configuring publishers in the adapter specific docs here:

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].