AWS DynamoDB

 DynamoDB allows users to create databases capable of storing and retrieving any amount of data and comes in handy while serving any amount of traffic. It dynamically manages each customer’s requests and provides high performance by automatically distributing data and traffic over servers. It is a fully managed NoSQL database service that is fast, predictable in terms of performance, and seamlessly scalable. It relieves the user from the administrative burdens of operating and scaling a distributed database as the user doesn’t have to worry about hardware provisioning, patching Softwares, or cluster scaling. It also eliminates the operational burden and complexity involved in protecting sensitive data by providing encryption at REST. 

DynamoDB Vs RDBMS

The below table provides us with core differences between a conventional relational database management system and AWS DynamoDB: 

OperationsDynamoDBRDBMS
Source connectionIt uses HTTP requests and API operations.It uses a persistent connection and SQL commands.
Create TableIt mainly requires the Primary key and no schema on the creation and can have various data sources.It requires a well-defined table for its operations.
Getting Table InformationOnly Primary keys are revealed.All data inside the table is accessible.
Loading Table DataIn tables, it uses items made of attributes.It uses rows made of columns.
Reading Table DataIt uses GetItem, Query, and ScanIt uses SELECT statements and filtering statements.
Managing IndexesIt uses a secondary index to achieve the same function. It requires specifications (partition key and sort key).Standard Indexes created by SQL is used.
Modifying Table DataIt uses a UpdateItem operation.It uses an UPDATE statement.
Deleting Table DataIt uses a DeleteItem operation.It uses a DELETE statement.
Deleting TableIt uses a DeleteTable operation.It uses a DROP TABLE statement.

Advantage of DynamoDB:

The main advantages of opting for Dynamodb are listed below: 

  • It has fast and predictable performance.
  • It is highly scalable.
  • It offloads the administrative burden operation and scaling.
  • It offers encryption at REST for data protection.
  • Its scalability is highly flexible.
  • AWS Management Console can be used to monitor resource utilization and performance metrics.
  • It provides on-demand backups.
  • It enables point-in-time recovery for your Amazon DynamoDB tables. Point-in-time recovery helps protect your tables from accidental write or delete operations. With point-in-time recovery, you can restore that table to any point in time during the last 35 days.
  • It can be highly automated. 
     

Limitations of DynamoDB –

The below list provides us with the limitations of Amazon DynamoDB: 

  • It has a low read capacity unit of 4kB per second and a write capacity unit of 1KB per second.
  • All tables and global secondary indexes must have a minimum of one read and one write capacity unit.
  • Table sizes have no limits, but accounts have a 256 table limit unless you request a higher cap.
  • Only Five local and twenty global secondary (default quota) indexes per table are permitted.
  • DynamoDB does not prevent the use of reserved words as names.
  • Partition key length and value minimum length sits at 1 byte, and maximum at 2048 bytes, however, DynamoDB places no limit on values.

Comments

Post a Comment

Popular posts from this blog

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Agile Retrospective

Image
  Guide to agile retrospectives for continuous improvement An agile retrospectives is an opportunity for agile development teams to reflect on past work together and identify ways to improve. Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). During the agile retrospective, the team discusses what went well, what did not go as planned, and how to make the next work period better. Even if you are not on a development team, you can probably relate to the concept of retrospection. Have you ever worked hard on something only to realize later that you should have done it differently? It is not always a good feeling, but the solutions you uncover in hindsight can be valuable input for your next try. The same goes for your successes — acknowledging what went well and is worth repeating can be just as impactful. What is an agile retrospective? In short, an agile retrospective is a meeting...
Read more

Agile product management

Image
  What is agile product management? How do we define agile product management? It is a product development philosophy that emphasizes a flexible and human — rather than a rigid process- or tool-oriented — approach to defining product strategy and carrying out work. Teammates focus heavily on customer feedback to make improvements and adjust roadmaps throughout the product management process. This creates more responsive teams, leads to quicker iterations, and creates a more lovable experience overall. Benefits of agile product management Agile redefines how product managers think about planning and building products. Traditionally, new customer experiences were planned, designed, implemented, and tested in a step-by-step way. This meant that new functionality was delivered sequentially. Once requirements were defined and handed off to the development team, it was difficult to make any changes. The failure rate of large-scale and lengthy software development proj...
Read more