-
Notifications
You must be signed in to change notification settings - Fork 11
Home
phachon edited this page Jun 6, 2018
·
4 revisions
WMQX working principle is as follows:
- There is no need to connect to RabbitMQ, providing a high-performance, highly available HTTP interface to manage messages
- To help users realize the consumption process, they only need to add the corresponding consumer API through the interface to realize the consumption or message push
- Each consumer is handled by a separate goroutine, and consumers consume each other independently
- Simple and convenient deployment, support cross-platform deployment, low use and access costs
- The WMQX consuming process forwards the original request information to the corresponding consumer URL by sending the message through the HTTP publishing interface
- Provide a complete set of background management UI, see WMQX-UI
If you don't have a RabbitMQ service, you'll need to install it yourself, which is pretty simple, see http://www.rabbitmq.com/download.html
Download the latest binary from https://github.com/phachon/wmqx/releases
# Unpack
$ tar -zxvf wmqx.tar.gz
# The default configuration file USES wmqx.conf in the current directory
$ cp config.toml wmqx.conf
# config wmqx.conf
[rabbitmq]
host = "RabbitMQ Server Ip"
port = 5672
username = "test"
password = "123456"
vhost = "/"
# start run
$ ./wmqx
# Of course, you can also specify the configuration file path to start
$ ./wmqx --conf wmqx.conf