Sign-up now and get instant access
Leave a comment
Customized training to master new skills and grow your business.
Beginner to advanced classes taught by Microsoft MVPs and Authors.
In-depth boot camps take you from a novice to mastery in less than a week.
Season Learning Pass
Get access to our very best training offerings for successful up-skilling.
Stream Pro Plus
Combine On-Demand Learning platform with face-to-face Virtual Mentoring.
Quick references for when you need a little guidance.
Summaries developed in conjunction with our Learn with the Nerds sessions.
Digital goodies - code samples, student files, and other must have files.
Stay up-to-date on all things Power BI, Power Apps, Microsoft 365 and Azure.
Earn money by driving sales through the Pragmatic Works' Training Affiliate Program.
It's time to address your client's training needs.
Learn how to get into IT with free training and mentorship.
Discover the faces behind our success: Meet our dedicated team
How can we help? Connect with Our Team Today!
Find all the information you’re looking for. We’re happy to help.
Today I’d like to walk through the multi model database portion of Cosmos DB and explain what multi model means to you. Multi model database service means that your data can be stored a number of different ways. Currently, Cosmos DB stores 4 different types of data and it allows you to integrate with an API and build out a user experience around these database storage types.
Let’s take a look at the models of storage with Cosmos DB:
1. Document DB or Mongo DB – Both work with document databases. A SQL API works with document DB protocols. The Mongo DB works with Mongo APIs. We store the data in a JSON (or similar) format and either of those APIs allow you to interact with those documents in the database. It’s easiest to use a SQL API if you’re starting from scratch, as it’s the most native version of working with Cosmos.
If you have a Mongo database solution and you want to look at making it globally aware or scaling it out, you can move it directly into Cosmos DB and use a Mongo DB API to interact with that data.
2. Graph Database – Similar to what you use with Facebook to understand how the data is related and works together. Microsoft has chosen to use the Gremlin API from Apache TinkerPop. So, they’re using an open source API that already exists, enabling you to interact with a graph database globally scaled with all the Cosmos features in Apache.
3. Key Value Pair – Another way to store your data with the key and values associated with that. This solution is supported on the standard Azure table API, which follows the same schema and design as Azure table storage.
4. Wide Column or Column Family – In this scenario, Microsoft leverages the Cassandra API. If you have Cassandra implementation, you can move that to Cosmos DB and use the wide column format that is used in Cassandra.
Keep in mind, choosing the API is not the end all. The data is stored there, so the APIs give you the chance to pick and choose how you interact with the data and how that data is optimized in the database on the back end. If you have workloads that work around one of these models, it’s a great option to look at as you move forward in your Azure journey.
If you have questions or want to learn more about using Cosmos DB in your environment or need help with anything Azure related, you’re in the right place. Click the link below or contact us—we’re here to help.
Join other Azure, Power Platform and SQL Server pros by subscribing to our blog.