Riak at Braintree

Why Braintree chose Riak as a highly available data store and how it uses Riak in Rails applications.

Transcript

1. Riak at Braintree Ben Mills
2. Braintree?
3. Challenges * 150 requests/second at peak * Majority of requests are meaningful * Write heavy * Zero downtime
4. Why Riak?
5. Databases * MySQL * PostgreSQL * MongoDB
6. MongoDB * Scaling writes * Replica Sets * Disk space
7. Riak * Extremely scalable * Straightforward setup * Supporting company and community * Erlang
8. HA at Braintree * Broxy * Load balancers * DRBD
9. Active/Active * Multiple data centers * Pacemaker * PostgreSQL
10. How we use Riak
11. Curator * Decouple persistence and domain * Swappable storage backend * Testability
12. class Person include Curator::Model attr_accessor :id, :first_name, :last_name, :age end
13. class PersonRepository include Curator::Repository indexed_fields :age end
14. person = Person.new( :first_name => "Ben", :last_name => "Mills" :age => 24 ) PersonRepository.save(person) PersonRepository.find_by_id(person.id) PersonRepository.find_by_age(24)
15. Migrations
16. class Person include Curator::Model attr_accessor :id, :age def name if @name @name else “#{@first_name} #{last_name}” end end end
17. class PersonRepository include Curator::Repository indexed_fields :age def self.deserialize(p) if !p.has_key?(:name) p[:name] = “#{p[:first_name]} #{p[:last_name]}” end p end end
18. Lazy Migrations
19. class Person include Curator::Model version 1 attr_accessor :id, :name, :age end
20. class ConsolidateName < Curator::Migration def migrate(attributes) first_name = attributes.delete(:first_name) last_name = attributes.delete(:last_name) attributes.merge(:name => "#{first_name} #{last_name}") end end
21. Q/A
22. We’re hiring joinbraintree.com
23. Thank you! twitter.com/benemills github.com/benmills Ben Mills