Loopback dynamo model to provide which endpoints to share
DynamoDB client for NodeJS and browser with a fluent api to build requests. We take care of the type mapping between JS and DynamoDB, customizable trough typescript decorators.
Dynamic NodeTS (NodeJS-Typescript), MongoDB Backend System Framework by Future Development Program Ltd.
Full Stack Model Collection for Dynamic (NodeJS-Typescript) Framework called Dynamo, by Future Development Ltd.
Abstraction of AWS DynamoDB API
A lightweight and promise-based wrapper of the AWS SDK to create and delete tables.
A collection of converter functions to get good old JavaScript key/value objects into a DynamoDB friendly schema and back again.
A wrapper around Amazon's DynamoDB Local to start and stop it from Node.js.
No description provided.
Adds higher-level methods to dynamo-table
Storage for :mega: stentor using AWS DynamoDB
DynamoDB storage adapter for Keyv
An AWS CDK construct which exposes an endpoint with the contents of a DynamoDB table
Entity Storage connector implementation using DynamoDb storage
ProseMirror's document model
Serverless Plugin to deploy DynamoDB Autoscaling
Simple powerful data modeling primitives for DynamoDB in JavaScript.
Get accurate and well named css box model information about an Element 📦
Parser and generator for CSS color strings
Common functions and wrappers used in Sardius APIs
Define DynamoDB tables using TypeScript decorators - type-safe, declarative infrastructure with Lafken
DynamoDB store for Seneca
GUI for DynamoDB. Useful for local development.
This library was generated with [Nx](https://nx.dev).
Ccom objetivo de agilizar e simplicar o trabalho com o dynamoDB, essa biblioteca vai ajudar a abstrair as funcões do dynamoDB
== 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
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.