Bobcares

Atomic Counter in AWS DynamoDB with AWS CLI: Setup

by | Apr 5, 2023

Let us look at how to set up atomic counter in AWS DynamoDB with AWS CLI. With the support of our AWS support services at Bobcares we will learn how to set this feature up.

Why set up Atomic counter in AWS DynamoDB with AWS CLI?

It would often be beneficial if we could track some numerical data, such as website visits that are incremental in nature. Such counts must be kept in a centralized location, and updates must be atomic.

Atomic means that one request runs without interfering with another. Concurrent updates do not conflict with one another, therefore we won’t lose any data in the process.

As everyone is using ephemeral infrastructure like EC2, which is being replaced by Auto Scaling groups or containers, holding such a counter locally is not a smart idea.

DDB is the greatest solution for central storage since it is an ultra-fast, single-digit millisecond latency NoSQL database. Excellent for scaling infrared/traffic at the atomic level.

Let’s get started on generating and updating this counter.

Building the counter’s AWS DynamoDB table with CLI

This is the first step in setting up atomic counter in AWS DynamoDB with AWS CLI.

  1. Log in to the DDB console.
  2. Choose Create table.
  3. Put the name of the table here.
  4. Enter the Main Key (Partition Key).
  5. We don’t need a sort key in this case because our table will only contain one counter value. Leave the rest of the settings alone and click Create.

Create a DynamoDB table

To construct a DDB table, we may utilize the Cloudformation resource block shown below:

Getting a DynamoDB database ready for counter updates

This is the next step to set up the atomic counter in AWS DynamoDB with AWS CLI. The new table information will open up. Go to the Items tab and select Create item.

After that, create a DynamoDB Item and add the specifications to the item. Save the file. The DDB table is now available for counter updates. We can use the Amazon CLI to create DDB tables, as seen below:

$ aws dynamodb put-item --table-name kerneltalks-counter --item '{"ID": { "S": "Counter" }, "TotalCount": { "N": "0" }}

Updating counter in DDB table

To update the counter, we may use the Amazon CLI command below. The counter will update itself by one every time we run the program.

We may write it in the application to execute this command/API call to update the counter.

The updated attribute in JSON format should be returned by the command. After that, we can convert it to text for using it in programming.

The same thing may be seen in the console. DDB is the counter.

That is the final steps in setting up the atomic counter in AWS DynamoDB with AWS CLI. We now have a counter in DDB that we can update from many sources via API calls.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now seen how to set up the atomic counter in AWS DynamoDB with AWS CLI. With the support of our AWS support services team at Bobcares we have now gone through the whole setup process easily.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF