dfb0e91749
Change-Id: I834ab44acc48db07a196c3bbc1855d32d39ea62c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337902 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Build-Review: Isaac Moore <isaac.moore@instructure.com> Build-Review: Cody Cutrer <cody@instructure.com> QA-Review: Cody Cutrer <cody@instructure.com> Product-Review: Cody Cutrer <cody@instructure.com> |
||
---|---|---|
.. | ||
lib | ||
spec | ||
.rspec | ||
Gemfile | ||
Gemfile.lock | ||
README.md | ||
Rakefile | ||
canvas_dynamodb-0.0.1.gem | ||
canvas_dynamodb.gemspec |
README.md
Canvas DynamoDB
An opinionated way to talk to Dynamo tables.
Features
- Query Logging : statements that get executed will get written to rails debug logs
- Batch Operations: Useful helper methods for building batched read/write queries.
- Table Naming Conventions: using prefixes and semantic names.
Intentional Omissions!
We don't want to manage the tables themselves. A DynamoDB table is more like a database than a schema change. It should be managed in terraform and scaled by devops tooling.