DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

How does AI transform chaos engineering from an experiment into a critical capability? Learn how to effectively operationalize the chaos.

Data quality isn't just a technical issue: It impacts an organization's compliance, operational efficiency, and customer satisfaction.

Are you a front-end or full-stack developer frustrated by front-end distractions? Learn to move forward with tooling and clear boundaries.

Developer Experience: Demand to support engineering teams has risen, and there is a shift from traditional DevOps to workflow improvements.

Related

  • Engineering Resilience Through Data: A Comprehensive Approach to Change Failure Rate Monitoring
  • Taming Billions of Rows: How Metadata and SQL Can Replace Your ETL Pipeline
  • Defining Effective Microservice Boundaries - A Practical Approach To Avoiding The Most Common Mistakes
  • Zero-Latency Architecture: Database Triggers + Serverless Functions for Modern Reactive Architectures

Trending

  • TFVC to Git Migration: Step-by-Step Guide for Modern DevOps Teams
  • DevOps in the Cloud - How to Streamline Your CI/CD Pipeline for Multinational Teams
  • Zero-Latency Architecture: Database Triggers + Serverless Functions for Modern Reactive Architectures
  • Operationalizing Data Quality in Cloud ETL Workflows: Automated Validation and Anomaly Detection
  1. DZone
  2. Data Engineering
  3. Databases
  4. Query DynamoDB Items With Node.js

Query DynamoDB Items With Node.js

We have a look at querying data in DynamoDB using Node.js along with some example code.

By 
Emmanouil Gkatziouras user avatar
Emmanouil Gkatziouras
DZone Core CORE ·
Jul. 07, 16 · Tutorial
Likes (3)
Comment
Save
Tweet
Share
68.0K Views

Join the DZone community and get the full member experience.

Join For Free

In a previous post, we tackled inserting data into a DynamoDB database.

In this tutorial, we will issue some basic queries against our DynamoDB tables.

The main rule is that every query has to use the hash key.

The simplest form of query is using the hash key only. We will query the Users table on this one. There would be only one result, therefore there is no use iterating the Items list.

var getUser = function(email,callback) {

    var docClient = new AWS.DynamoDB.DocumentClient();

    var params = {
        TableName: "Users",
        KeyConditionExpression: "#email = :email",
        ExpressionAttributeNames:{
            "#email": "email"
            },
        ExpressionAttributeValues: {
            ":email":email
            }
        };

    docClient.query(params,callback);
    };


However, we can issue more complex queries using conditions. The Logins Table works well for an example. We will issue a query that will fetch login attempts between to dates.

var queryLogins = function(email,from,to,callback) {

    var docClient = new AWS.DynamoDB.DocumentClient();

    var params = {
        TableName:"Logins",
        KeyConditionExpression:"#email = :emailValue and #timestamp BETWEEN :from AND :to",
        ExpressionAttributeNames: {
            "#email":"email",
            "#timestamp":"timestamp"
            },
        ExpressionAttributeValues: {
            ":emailValue":email,
            ":from": from.getTime(),
            ":to":to.getTime()
            }
        };

    var items = []

    var queryExecute = function(callback) {

        docClient.query(params,function(err,result) {

            if(err) {
                callback(err);
                } else {

                console.log(result)

                items = items.concat(result.Items);

                if(result.LastEvaluatedKey) {

                    params.ExclusiveStartKey = result.LastEvaluatedKey;
                    queryExecute(callback);
                    } else {
                        callback(err,items);
                    }
                }
            });
        }

        queryExecute(callback);
    };

Keep in mind that DynamoDB fetches data in pages, therefore you have to issue the same request more than once in the case of multiple pages. You have to use the last evaluated key to your next request. If there are a lot of entries, be aware that you should handle the call stack size.

Last but not least, querying on indexes is one of the basic actions. It is the same routine either for local or global secondary indexes. Keep in mind that the results fetched depend on the projection type we specified once creating the Table. In our case, the projection type is for all fields.

We shall use the Supervisors table.

var docClient = new AWS.DynamoDB.DocumentClient();

var params = {
    TableName: "Supervisors",
    IndexName: "FactoryIndex",
    KeyConditionExpression:"#company = :companyValue and #factory = :factoryValue",
    ExpressionAttributeNames: {
        "#company":"company",
        "#factory":"factory"
        },
    ExpressionAttributeValues: {
        ":companyValue": company,
        ":factoryValue": factory
        }
    };

docClient.query(params,callback);


You can find full source code with unit tests on GitHub.

Related Refcard:

Node.js

Database

Published at DZone with permission of Emmanouil Gkatziouras, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Engineering Resilience Through Data: A Comprehensive Approach to Change Failure Rate Monitoring
  • Taming Billions of Rows: How Metadata and SQL Can Replace Your ETL Pipeline
  • Defining Effective Microservice Boundaries - A Practical Approach To Avoiding The Most Common Mistakes
  • Zero-Latency Architecture: Database Triggers + Serverless Functions for Modern Reactive Architectures

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: