0.02
No release in over 3 years
== OceanDynamo As one important use case for OceanDynamo is to facilitate the conversion of SQL databases to no-SQL DynamoDB databases, it is important that the syntax and semantics of OceanDynamo are as close as possible to those of ActiveRecord. This includes callbacks, exceptions and method chaining semantics. OceanDynamo follows this pattern closely and is of course based on ActiveModel. The attribute and persistence layer of OceanDynamo is modeled on that of ActiveRecord: there's +save+, +save!+, +create+, +update+, +update!+, +update_attributes+, +find_each+, +destroy_all+, +delete_all+, +read_attribute+, +write_attribute+ and all the other methods you're used to. The design goal is always to implement as much of the ActiveRecord interface as possible, without compromising scalability. This makes the task of switching from SQL to no-SQL much easier. OceanDynamo uses only primary indices to retrieve related table items and collections, which means it will scale without limits. OceanDynamo is fully usable as an ActiveModel and can be used by Rails controllers. Thanks to its structural similarity to ActiveRecord, OceanDynamo works with FactoryBot. See also Ocean, a Rails framework for creating highly scalable SOAs in the cloud, in which ocean-dynamo is used as a central component: http://wiki.oceanframework.net
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
 Dependencies