Search This Blog

Showing posts with label dynamo. Show all posts
Showing posts with label dynamo. Show all posts

Sunday, 5 July 2020

Dynamo Db - locks continued

In the last post I used optimistic locking with the Version attribute provided by DynamoDBMapper. Here I am going to look at the pessimistic locking method

Friday, 26 June 2020

Dynamo Db - locks

When I studies Databases in college, we learnt the concept of locks
A database lock is used to “lock” some data in a database so that only one 
database user/session may update that particular data. So, database locks 
exist to prevent two or more database users from updating the same exact 
piece of data at the same exact time.
The idea was to achieve transactional isolation. Or two operations operating on the same record did not have any side effects on the other.

Thursday, 18 June 2020

Dynamo Db - Good To Remember stuff

Post is a collection of interesting pointers on the working of Dynamo Db. I wanted to have them in a single place as a ready reference

Thursday, 4 June 2020

Dynamo Db's API Model

While doing a search for Dynamo Db get Item code, I came across several different code samples (obviously) and also realized a not so obvious thing - there are multiple ways to access Dynamo Db through code.

Tuesday, 2 June 2020

More on DAX

In the previous post we setup a DAX client and tested the GetItem performance. This post will look at other DAX features

Sunday, 31 May 2020

DAX - speeding/cheapening up Dynamo Db

Amazon DynamoDb comes with its own cache layer DAX or DynamoDB Accelerator. In this post I am going to play around with this feature.

Monday, 25 May 2020

Dynamo Db APIs through API Gateway

In the last post, we setup a GET method for my table through API Gateway. I wanted to go ahead and setup the other methods - DELETE, PUT, POST.

Sunday, 24 May 2020

REST + Dynamo = API Gateway

My use case is very straight forward - I have a table and I want to expose CRUD operations on the table - GET, ADD, DELETE, UPDATE.

Saturday, 9 May 2020

Step Functions - AWS Service Integrations

With all this serverless chatter around Lambda, the next thing was to try and orchestrate these Lambdas with Step Functions. Essentially a Step Function allows you to define the steps to be executed across systems in a visual UI. The interactions, retries, failure conditions and other orchestration behavior (or the flow management) can be done by Step Functions.