rabbitmq   4137

« earlier    

Why We Chose Kafka For The Trello Socket Architecture
RT : Great read on why changed from to
"Why We Chose Kafka For The Trello Socket Architecture"
Trello  RabbitMQ  Kafka  from twitter_favs
12 days ago by pdudits
Airport Baggage Claims, Selective Consumers, and RabbitMQ Anti-Patterns - DerickBailey.com
On designs based on conditionally reject a message after having received it, by abusing NACK. Of course, RabbitMQ routing should be used to ensure this never happens.
RabbitMQ  messageBrokering  designPatterns  antiPatterns  blogEntries 
18 days ago by MaxBarraclough
RabbitMQ tutorial - Routing
For multiple recipients, the pattern seems to be to have each consumer create and configure an 'ephemeral' queue (whose name is *not* well-known), and to have the exchange and routing-key (binding-key) names well-known, as it is their names which the producers care about. Recall that a queue can be bound to multiple exchanges, so with this pattern, a queue approximates a consumer/recipient.

Using multiple consumers with a single queue, only makes sense for round-robin

fanout exchanges are documented at https://www.rabbitmq.com/tutorials/tutorial-three-python.html

topic exchanges at https://www.rabbitmq.com/tutorials/tutorial-five-python.html
RabbitMQ  AMQP  messageBrokering 
18 days ago by MaxBarraclough
RabbitMQ in 5 Minutes
A pretty good, very quick, introduction to RabbitMQ/AMQP concepts
RabbitMQ  messageBrokering  YouTubeVideos  videos 
18 days ago by MaxBarraclough
Is it possible to view RabbitMQ message contents directly from the command line? - Stack Overflow
I had to do a very strange cd to get `python cli/rabbitmqadmin....` to work -- to a directory named ..../rabbitmq_management-3.7.7/priv/www
RabbitMQ  StackOverflow  sysAdmin 
19 days ago by MaxBarraclough
RabbitMQ Start fails when I recreate a VM with same storage and run chef converge again · Issue #455 · rabbitmq/chef-cookbook
> timeout_waiting_for_tables means that a node could not contact a known peer to sync internal database from. Before RabbitMQ 3.6.7, there is only one timeout, rabbit. mnesia_table_loading_timeout, which is 30 seconds by default.

> Starting with 3.6.7, there are two settings:

> rabbit.mnesia_table_loading_retry_limit, the number of retries, 10 by default
rabbit. mnesia_table_loading_retry_timeout, a timeout per attempt, 30s by default.
We highly recommend upgrading to 3.6.10 and adjusting those two as needed in rabbitmq.config. 10 retries with a 30s timeout each is sufficient in most cases but 30s prior to 3.6.7 can be too low.
github  rabbitmq 
23 days ago by atomicules

« earlier    

related tags

10up  amqp  and  ansible-playbook  ansible  ansynchronous  antipatterns  apache  apache_kafka  api  architecture  aspnetcore  aws  backend  blog  blogentries  blogs  bugs  celery  cluster  communication  comparison  configuration  container  deployment  designpatterns  development  distributed-systems  distributed  django  dlq  docker  dockerfile  documentation  dzone  elixir  erlang  events  example  features  gearman  github  go  golang  guide  gunicorn  howto  hub  installation  integrate  integration  java  job  k8s  kafka  kubernetes  locking  mailing_list  masstransit  memcached  message  messagebrokering  messagequeue  messaging  microservices  ml  mnesia  mq  mulesoft  nginx  performance  phoenix  plug  plugin  postgis  postgres  programming  prometheus  protocol  pubsub  python  queue  queueing  rabbit  rabbitmq_performance  rails  read2of  realtime  redis  reference  requirements  resilience  rest  retrystrategy  ruby  ryan_mccue  scs  sidekiq  ssl  stackoverflow  sysadmin  testing  tolearn  toread  totry  tounderstand  trello  tutorial  twitter  uwsgi  version  videos  webdev  with  wp  xmpp  youtubevideos 

Copy this bookmark: