Dynamoid

Dynamoid is an ORM for Amazon's DynamoDB for Ruby applications. It
provides similar functionality to ActiveRecord and improves on
Amazon's existing
HashModel
by providing better searching tools and native association support.

DynamoDB is not like other document-based databases you might know, and is very different indeed from relational databases. It sacrifices anything beyond the simplest relational queries and transactional support to provide a fast, cost-efficient, and highly durable storage solution. If your database requires complicated relational queries and transaction support, then this modest Gem cannot provide them for you, and neither can DynamoDB. In those cases you would do better to look elsewhere for your database needs.

But if you want a fast, scalable, simple, easy-to-use database (and a Gem that supports it) then look no further!

Alternatively, if you don't want Aws connection settings to be overwritten for you entire project, you can specify connection settings for Dynamoid only, by setting those in the Dynamoid.configure clause:

Then you need to initialize Dynamoid config to get it going. Put code similar to this somewhere (a Rails initializer would be a great place for this if you're using Rails):

Dynamoid.configuredo|config|config.namespace="dynamoid_app_development"# To namespace tables created by Dynamoid from other tables you might have. Set to nil to avoid namespacing.config.endpoint='http://localhost:3000'# [Optional]. If provided, it communicates with the DB listening at the endpoint. This is useful for testing with [Amazon Local DB] (http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.DynamoDBLocal.html).end

Compatibility Matrix

Ruby / Active Record

4.0.x

4.1.x

4.2.x

5.0.x

2.0.0

✓

✓

✓

2.1.x

✓

✓

✓

2.2.0-2.2.1

✓

✓

✓

2.2.2+

✓

✓

✓

✓

2.3.x

✓

✓

✓

✓

2.3.x

✓

✓

✓

✓

2.4.x

✓

✓

jruby-9.X

✓

✓

✓

✓

Setup

You must include Dynamoid::Document in every Dynamoid model.

classUserincludeDynamoid::Documentend

Table

Dynamoid has some sensible defaults for you when you create a new table, including the table name and the primary key column. But you can change those if you like on table creation.

These fields will not change an existing table: so specifying a new read_capacity and write_capacity here only works correctly for entirely new tables. Similarly, while Dynamoid will look for a table named awesome_users in your namespace, it won't change any existing tables to use that name; and if it does find a table with the correct name, it won't change its hash key, which it expects will be user_id. If this table doesn't exist yet, however, Dynamoid will create it with these options.

Fields

You'll have to define all the fields on the model and the data type of each field. Every field on the object must be included here; if you miss any they'll be completely bypassed during DynamoDB's initialization and will not appear on the model objects.

By default, fields are assumed to be of type :string. Other built-in types are
:integer, :number, :set, :array, :datetime, date, :boolean, :raw and :serialized.
raw type means you can store Ruby Array, Hash, String and numbers.
If built-in types do not suit you, you can use a custom field type represented by an arbitrary class, provided that the class supports a compatible serialization interface.
The primary use case for using a custom field type is to represent your business logic with high-level types, while ensuring portability or backward-compatibility of the serialized representation.

Note on boolean type

The boolean fields are stored as "t", "f" strings by default. DynamoDB
supports boolean type natively. So if you want to use native boolean
type or already have table with native boolean attribute you can easily
achieve this with store_as_native_boolean option:

If you want to use a third-party class (which does not support #dynamoid_dump and .dynamoid_load)
as your field type, you can use an adapter class providing .dynamoid_dump and .dynamoid_load class methods
for your third-party class. (.dynamoid_load can remain the same from the previous example; here we just
add a level of indirection for serializing.) Example:

Lastly, you can control the data type of your custom-class-backed field at the DynamoDB level.
This is especially important if you want to use your custom field as a numeric range or for
number-oriented queries. By default custom fields are persisted as a string attribute, but
your custom class can override this with a .dynamoid_field_type class method, which would
return either :string or :number.

DynamoDB may support some other attribute types that are not yet supported by Dynamoid.

Associations

Just like in ActiveRecord (or your other favorite ORM), Dynamoid uses associations to create links between models.

The only supported associations (so far) are has_many, has_one, has_and_belongs_to_many, and belongs_to. Associations are very simple to create: just specify the type, the name, and then any options you'd like to pass to the association. If there's an inverse association either inferred or specified directly, Dynamoid will update both objects to point at each other.

classUserincludeDynamoid::Document# ...has_many:addresseshas_many:students,:class=>Userbelongs_to:teacher,:class_name=>:userbelongs_to:groupbelongs_to:group,:foreign_key=>:group_idhas_one:rolehas_and_belongs_to_many:friends,:inverse_of=>:friending_usersendclassAddressincludeDynamoid::Document# ...belongs_to:user# Automatically links up with the user modelend

Contrary to what you'd expect, association information is always contained on the object specifying the association, even if it seems like the association has a foreign key. This is a side effect of DynamoDB's structure: it's very difficult to find foreign keys without an index. Usually you won't find this to be a problem, but it does mean that association methods that build new models will not work correctly -- for example, user.addresses.new returns an address that is not associated to the user. We'll be correcting this ~soon~ maybe someday, if we get a pull request.

Validations

Dynamoid bakes in ActiveModel validations, just like ActiveRecord does.

Usage

Object Creation

Dynamoid's syntax is generally very similar to ActiveRecord's. Making new objects is simple:

u=User.new(:name=>'Josh')u.email='josh@joshsymonds.com'u.save

Save forces persistence to the datastore: a unique ID is also assigned, but it is a string and not an auto-incrementing number.

u.id# => "3a9f7216-4726-4aea-9fbc-8554ae9292cb"

To use associations, you use association methods very similar to ActiveRecord's:

address=u.addresses.createaddress.city='Chicago'address.save

To create multiple documents at once:

User.create([{name:'Josh'},{name:'Nick'}])

There is an efficient and low-level way to create multiple documents
(without validation and callbacks running):

users=User.import([{name:'Josh'},{name:'Nick'}])

Querying

Querying can be done in one of three ways:

Address.find(address.id)# Find directly by ID.Address.where(:city=>'Chicago').all# Find by any number of matching criteria... though presently only "where" is supported.Address.find_by_city('Chicago')# The same as above, but using ActiveRecord's older syntax.

And you can also query on associations:

u.addresses.where(:city=>'Chicago').all

But keep in mind Dynamoid -- and document-based storage systems in general -- are not drop-in replacements for existing relational databases. The above query does not efficiently perform a conditional join, but instead finds all the user's addresses and naively filters them in Ruby. For large associations this is a performance hit compared to relational database engines.

Limits

There are three types of limits that you can query with:

record_limit - The number of evaluated records that are returned by the query.

scan_limit - The number of scanned records that DynamoDB will look at before returning.

batch_size - The number of records requested to DynamoDB per underlying request, good for large queries!

Using these in various combinations results in the underlying requests to be made in the smallest size possible and
the query returns once record_limit or scan_limit is satisfied. It will attempt to batch whenever possible.

You can thus limit the number of evaluated records, or select a record from which to start, to support pagination:

If you are potentially running over a large data set and this is especially true when using certain filters, you may
want to consider limiting the number of scanned records (the number of records DynamoDB infrastructure looks through
when evaluating data to return):

Address.scan_limit(5).start(address)# Only scan at most 5 records and return what's found starting from `address`

For large queries that return many rows, Dynamoid can use AWS' support for requesting documents in batches:

# Do some maintenance on the entire table without flooding DynamoDBAddress.all(batch_size:100).each{|address|address.do_some_work;sleep(0.01)}Address.record_limit(10_000).batch(100).each{

The implication of batches is that the underlying requests are done in the batch sizes to make the request and responses
more manageable. Note that this batching is for Query and Scans and not BatchGetItem commands.

Sort Conditions and Filters

You are able to optimize query with condition for sort key. Following operators are available: gt, lt, gte, lte,
begins_with, between as well as equality:

Consistent Reads

Querying supports consistent reading. By default, DynamoDB reads are eventually consistent: if you do a write and then a read immediately afterwards, the results of the previous write may not be reflected. If you need to do a consistent read (that is, you need to read the results of a write immediately) you can do so, but keep in mind that consistent reads are twice as expensive as regular reads for DynamoDB.

Address.find(address.id,:consistent_read=>true)# Find an address, ensure the read is consistent.Address.where(:city=>'Chicago').consistent.all# Find all addresses where the city is Chicago, with a consistent read.

Range Finding

If you have a range index, Dynamoid provides a number of additional other convenience methods to make your life a little easier:

It also supports .gte and .lte. Turning those into symbols and allowing a Rails SQL-style string syntax is in the works. You can only have one range argument per query, because of DynamoDB's inherent limitations, so use it sensibly!

Deleting

In order to delete some items delete_all method should be used.
Any callback wont be called. Items delete in efficient way in batch.

projected_attributes - list of fields to store in an index or has a predefiled value :keys_only, :all; :keys_only is a default,

name - an index will be created with this name when a table is created; by default name is generated and contains table name and keys names,

read_capacity - is used when table creates and used as an index capacity; by default equals Dynamoid::Config.read_capacity,

write_capacity - is used when table creates and used as an index capacity; by default equals Dynamoid::Config.write_capacity

The only mandatory option is name.

To use index in Document.where implicitly you need to project all the fields with option projected_attributes: :all.

There are two ways to query Global Secondary Indexes (GSI).

Explicit

The first way explicitly uses your GSI and utilizes the find_all_by_secondary_index method which will lookup a valid
GSI to use based on the inputs, you MUST provide the correct keys to match the GSI you want:

find_all_by_secondary_index({dynamo_primary_key_column_name=>dynamo_primary_key_value},# The signature of find_all_by_secondary_index is ugly, so must be an explicit hash here:range=>{"#{range_column}.#{range_modifier}"=>range_value},# false is the same as DESC in SQL (newest timestamp first)# true is the same as ASC in SQL (oldest timestamp first):scan_index_forward=>false# or true)

Where the range modifier is one of Dynamoid::Finders::RANGE_MAP.keys, where the RANGE_MAP is:

Most range searches, like eq, need a single value, and searches like between, need an array with two values.

Implicit

The second way implicitly uses your GSI through the where clauses and deduces the index based on the query fields
provided. Another added benefit is that it is built into query chaining so you can use all the methods used in normal
querying. The explicit way from above would be rewritten as follows:

The only caveat with this method is that because it is also used for general querying, it WILL NOT use a GSI unless it
explicitly has defined projected_attributes: :all on the GSI in your model. This is because GSIs that do not have all
attributes projected will only contain the index keys and therefore will not return objects with fully resolved field
values. It currently opts to provide the complete results rather than partial results unless you've explicitly looked up
the data.

Future TODO could involve implementing select in chaining as well as resolving the fields with a second query against
the table since a query against GSI then a query on base table is still likely faster than scan on the base table

Configuration

Listed below are all configuration options.

adapter - usefull only for the gem developers to switch to a new adapter. Default and the only available value is aws_sdk_v2

batch_size - when you try to load multiple items at once with batch_get_item call Dynamoid loads them not with one api call but piece by piece. Default is 100 items

read_capacity - is used at table or indices creation. Default is 100 (units)

write_capacity - is used at table or indices creation. Default is 20 (units)

warn_on_scan - log warnings when scan table. Default is true

endpoint - if provided, it communicates with the DynamoDB listening at the endpoint. This is useful for testing with [Amazon Local DB]

identity_map - ensures that each object gets loaded only once by keeping every loaded object in a map. Looks up objects using the map when referring to them. Isn't thread safe. Default is false.
Use Dynamoid::Middleware::IdentityMap to clear identity map for each HTTP request

timestamps - by default Dynamoid sets created_at and updated_at fields for model at creation and updating. You can disable this behavior by setting false value

sync_retry_wait_seconds - time to wait between retries. Default is 2 (seconds)

convert_big_decimal - if true then Dynamoid converts numbers stored in Hash in raw field to float. Default is false

models_dir - dynamoid:create_tables rake task loads DynamoDb models from this directory. Default is app/models. In Rails application you should set ./app/models value

application_timezone - Dynamoid converts all datetime fields to specified time zone when loads data from the storage.
Acceptable values - utc, local (to use system time zone) and time zone name e.g. Eastern Time (US & Canada). Default is local

Concurrency

In this example, all saves to MyTable will raise an Dynamoid::Errors::StaleObjectError if a concurrent process loaded, edited, and saved the same row. Your code should trap this exception, reload the row (so that it will pick up the newest values), and try the save again.

Calls to update and update! also increment the lock_version, however they do not check the existing value. This guarantees that a update operation will raise an exception in a concurrent save operation, however a save operation will never cause an update to fail. Thus, update is useful & safe only for doing atomic operations (e.g. increment a value, add/remove from a set, etc), but should not be used in a read-modify-write pattern.

Rake Tasks

rake dynamoid:create_tables

rake dynamoid:ping

Test Environment

In test environment you will most likely want to clean the database between test runs to keep tests completely isolated. This can be achieved like so

In Rails, you may also want to ensure you do not delete non-test data accidentally by adding the following to your test environment setup:

raise"Tests should be run in 'test' environment only"ifRails.env!='test'Dynamoid.configuredo|config|config.namespace="#{Rails.application.railtie_name}_#{Rails.env}"end

Credits

Dynamoid borrows code, structure, and even its name very liberally from the truly amazing Mongoid. Without Mongoid to crib from none of this would have been possible, and I hope they don't mind me reusing their very awesome ideas to make DynamoDB just as accessible to the Ruby world as MongoDB.

Also, without contributors the project wouldn't be nearly as awesome. So many thanks to:

Running the tests

Running the tests is fairly simple. You should have an instance of DynamoDB running locally. Follow these steps to setup your test environment.

First download and unpack the latest version of DynamoDB. We have a script that will do this for you if you use homebrew on a Mac.

bin/setup

Start the local instance of DynamoDB to listen in 8000 port

bin/start_dynamodblocal

and lastly, use rake to run the tests.

rake

When you are done, remember to stop the local test instance of dynamodb

bin/stop_dynamodblocal

If you want to run all the specs that travis runs, use bundle exec wwtd, but first you will need to setup all the rubies, for each of %w( 2.0.0-p648 2.1.10 2.2.6 2.3.3 2.4.1 jruby-9.1.8.0 ). When you run bundle exec wwtd it will take care of starting and stopping the local dynamodb instance.

Copyright

Copyright (c) 2012 Josh Symonds.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.