index.html

---
title: Bunny, a dead easy to use RabbitMQ Ruby client
layout: default
---
<div class='headline'>
  <div class='logo'>
    <h1>Bunny</h1>
  </div>
  <div class='clear' style=''></div>
  <p style=''>
    A dead easy to use RabbitMQ Ruby client. Now feature complete.
  </p>
  <a class='btn btn-primary btn-large' href='/articles/getting_started.html'>Get Started! »</a>
  <a class="btn btn-large" href="/articles/guides.html">Read doc guides »</a>
  <a class='btn btn-large' href='http://groups.google.com/group/ruby-amqp'>Join the Mailing List »</a>
  <a class='btn btn-large' href='http://github.com/ruby-amqp/bunny'>Contribute »</a>
</div>
<div class='row-fluid'>
  <div class='span4'>
    <h3>Built to be easy to use</h3>
    <p>Bunny focuses on ease of use. Features, throughput, concurrency are important
       but ease of use comes first.</p>
  </div>
  <div class='span4'>
    <h3>Handles flaky networks</h3>
    <p>Bunny 0.9+ is designed with ops issues in mind. For example, it
    automatically reconnects and recovers channels after a network
    failure.</p>
  </div>
  <div class='span4'>
    <h3>Feature complete</h3>
    <p>Bunny 0.9+ supports all RabbitMQ 3.x features. No more hard choices.</p>
  </div>
</div>

<div class='row-fluid'>
  <div class='span4'>
    <h3>Hello, Multicore</h3>
    <p>Bunny 0.9+ is designed to make use of concurrency. On Ruby VMs that provide thread parallelism,
       this means taking advantage of multiple cores and CPUs.</p>
  </div>
  <div class='span4'>
    <h3>No heavy dependencies</h3>
    <p>Bunny does not depend on any opinionated networking libraries. No event loop
       blocking issues, no unfamiliar error messages.</p>
  </div>
  <div class='span4'>
    <h3></h3>
    <p></p>
  </div>
</div>