Cosmos DB Flashcards
atom-record-sequence
Core type system for CDB engine. CDB translates your data models into ARS
- atom - primitive types
- record - structs
- sequences - arrays
What are the consistency levels of CosmosDB?
- Strong
- Bounded Staleness
- Session
- Consistent Prefix
- Graph-based data
What do the different CosmosDB APIs allow you to do?
Use your existing API calls with CosmosDB. For example, CQL code to access Apache Cassandra DB can be simply ported over for use against CosmosDB
Difference between Azure Table storage and CosmosDB?
Azure Table storage is the predecessor of CosmosDB
Use cases for CosmosDB
Web, mobile, gaming, IoT apps that handle massive amounts of reads and writes at a global scale
Graph database
- Persist relationships in the storage layer
- Both entities(Nodes, AKA vertices) and their relationships(Edges, AKA Labels) to other entities are stored together using Properties(Somewhat like tags)
When Product A. is purchased, products C and D are usually purchased with it. You want to use these to make recommendations to your customers. What is the CosmosDB database/API type that should be used?
Graph
What does “multi-model” database service mean?
There are more than one data access methods (APIs) to access your data. (E;G., CosmosDB is multi-model)
How does the charging structure work for a CosmosDB table and why?
Charging is done by current capacity specified, regardless of the amount of data stored. This is because the capacity is reserved.
What are the 2 methods of migrating data to CosmosDB?
- CosmosDB Data Migration Tool
* AzCopy
Graph Database
One of the models supported by Cosmos DB.
Non-tabular format
Relationships are treated as data rather than schema structure
What is a Graph?
The essential structure of a graph database.
Comprised of
- Vertices/Nodes - represent objects
- Edges/Relationships - Relationships between vertices
- Properties - descriptors of vertices and edges
- Vertice Properties - description of the object
- Edge Properties - description of the relationship
What is the general way to define your Nodes and Edges in a graph database?
Nodes = nouns
- Customer
- Employee
- Product
Relationships = verbs - Likes
- Places
- Belongs To
BCDR
Business Continuity and Disaster Recovery
Multi-master support
- AKA multiple write regions
- Every region defined as a write region is considered a master
- data changes are automatically propagated with single digit latency