Faraday (DynamoDB) DataStore implementation for Tundra.
Use AWS Data Pipeline to setup scheduled backups of DynamoDB table(s) to S3 (there is a template pipeline for exactly this purpose).
Faraday (DynamoDB) DataStore implementation for Tundra. Use AWS Data Pipeline to setup scheduled backups of DynamoDB table(s) to S3 (there is a template pipeline for exactly this purpose).
(ensure-table client-opts
&
[{:keys [name throughput block?] :or {name default-table}}])Creates an appropriate Faraday Tundra table iff it doesn't already exist. Options: :name - Default is :faraday.tundra.datastore.default.prod. You may want additional tables for different apps/environments. :throughput - Default is {:read 1 :write 1}.
Creates an appropriate Faraday Tundra table iff it doesn't already exist.
Options:
:name - Default is :faraday.tundra.datastore.default.prod. You may
want additional tables for different apps/environments.
:throughput - Default is {:read 1 :write 1}.(faraday-datastore client-opts
&
[{:keys [table key-ns]
:or {table default-table key-ns :default}}])Alpha - subject to change. Returns a Faraday DataStore with options: :table - Tundra table name. Useful for different apps/environments with individually provisioned throughput. :key-ns - Optional key namespacing mechanism useful for different apps/environments under a single table (i.e. shared provisioned throughput). Supported Freezer io types: byte[]s.
Alpha - subject to change.
Returns a Faraday DataStore with options:
:table - Tundra table name. Useful for different apps/environments with
individually provisioned throughput.
:key-ns - Optional key namespacing mechanism useful for different
apps/environments under a single table (i.e. shared provisioned
throughput).
Supported Freezer io types: byte[]s.cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |