Project

em-bucketer

0.0
No release in over 3 years
Low commit activity in last 3 years
em-bucketerdgvz/em-bucketerHomepageDocumentationSource CodeBug TrackerWiki
A generic eventmachine library for storing arbitrary objects in buckets with callbacks on threshold reached
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
13,664
Stars
1
Forks
0
Watchers
2
 Releases
Current version
0.2.2
Total releases
5
First release
2014-11-01
Latest release
2014-11-04
 Development
Primary Language
Ruby
Licenses
GPL
Average date of last 50 commits
2014-12-30
Reverse Dependencies
0

 Dependencies

Development

bundler
~> 1.6
pry
>= 0
rake
>= 0
redis
>= 0
rspec
>= 0
yard
>= 0

Runtime

em-hiredis
>= 0
eventmachine
>= 0
 Project Readme

EventMachine::Bucketer

This is a generic EventMachine library for putting arbitrary objects into buckets and setting callbacks to be called when any bucket exceeds a specific threshold size. Although the Bucketer::InMemory is synchronous (it's just using a ruby hash) the interface is still what would be expected for an asynchronous API for consistency with other Bucketers that are actually asynchronous.

Installation

Add this line to your application's Gemfile:

gem 'em-bucketer'

And then execute:

$ bundle

Or install it yourself as:

$ gem install em-bucketer

Ordered Bucketer

The ordered bucketer adds items to buckets and gives them back in the same order in which they were put in.

Usage

require 'em-bucketer/ordered'
EM.run do

  ## InMemory with pop_all example
  bucketer = EM::Bucketer::Ordered::InMemory.new(:bucket_threshold_size => 5)

  bucketer.on_bucket_full do |bucket_id|
    p "yay bucket #{bucket_id} filled up!"

    bucketer.pop_all(bucket_id) do |items|
      EM.stop
      items.each do |item|
        p "got back #{item}"
      end
    end
  end

  bucketer.add_item("1", {:foo => :bar})
  bucketer.add_item("1", {:foo => :bar})
  bucketer.add_item("1", {:foo => :bar})
  bucketer.add_item("1", {:bar => :foo})
  bucketer.add_item("1", {:bar => :foo})

  ## Redis with pop_count example
  bucketer = EM::Bucketer::Ordered::Redis.new("my_prefix", :bucket_threshold_size => 5)

  bucketer.on_bucket_full do |bucket_id|
    p "yay bucket #{bucket_id} filled up!"

    bucketer.pop_count(bucket_id, 5) do |items|
      EM.stop
      items.each do |item|
        p "got back #{item}"
      end
    end
  end

  bucketer.add_item("1", {:foo => :bar})
  bucketer.add_item("1", {:foo => :bar})
  bucketer.add_item("1", {:foo => :bar})
  bucketer.add_item("1", {:bar => :foo})
  bucketer.add_item("1", {:bar => :foo})
end

Unordered Bucketer

The unordered bucketer requires you to pass in an 'id' which is used to ensure that no duplicates occur. This bucketer type should be used if you want to not have two of the same item in a bucket at one time. This type of bucketer does not guarantee that you get back items in the same order that they went in.

Usage

require 'em-bucketer'
EM.run do

  bucketer = EM::Bucketer::InMemory.new(:bucket_threshold_size => 5)

  bucketer.on_bucket_full do |bucket_id|
    p "yay bucket #{bucket_id} filled up!"

    bucketer.get_and_empty_bucket(bucket_id) do |items|
      EM.stop
      items.each do |item|
        p "got back #{item}"
      end
    end
  end

  bucketer.add_item("1", "1", {:foo => :bar})
  bucketer.add_item("1", "2", {:foo => :bar})
  bucketer.add_item("1", "3", {:foo => :bar})
  bucketer.add_item("1", "4", {:bar => :foo})
  bucketer.add_item("1", "5", {:bar => :foo})
end

Redis Bucketer

This gem also supports a redis backed bucketer which uses the em-hiredis gem. This bucketer uses Marshal.dump to store objects in redis and thus there are limitations on what can be placed in a bucket. Specifically you cannot store procs in buckets using the redis bucketer.

Contributing

  1. Fork it ( https://github.com/dgvz/em-bucketer/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request