CRUD Operations in Cosmos DB

Develop for Azure Storage

Shahzad Mian

Content developer, Datacamp

Create

• Primary way to communicate with Cosmos DB from an application is through SDKs

Read

• The app uses the SDK to read their specific document by its unique ID

Update

• The app finds their document and updates the points value from 100 to 0.

Delete

• Backend process uses the SDK to permanently delete their document from the container.

Choosing Your Consistency

• Consistency level choice - determines how quickly data changes are visible across locations.

Strong

• Strong - perfect accuracy, all locations must confirm before update is visible
• Slowest; ideal for financial transactions.

Boundless staleness

• Predictable and reliable reads.

Session

• Default and most popular option.
• Instantly readable.
• Consistent experience.
• Perfect for live user-centric applications.

Consistent prefix

• Changes always seen in the right order they were made.

• Not all changes are seen if they are made quickly.

• Correct sequence:

  • A few seconds behind the latest action.

Eventual

• Weakest level.
• No guarantee on timing or order.
• Lowest latency.

• Highest availability.

• Great for non critical data.

Fine tuning behavior

Let's practice!

Develop for Azure Storage