Podcast: Play in new window | Download
Different databases have different access patterns. Key-value, document, graph, and columnar databases are useful under different circumstances.
For example, if you are a bank, and you have a database of customers and the transactions they have performed, the ideal access pattern for aggregating the total amount of all transactions might be a columnar store. If the transaction amounts are all in one column, it helps to have all of the columnar entries close together on disk.
But if you want to look at your bank as a social network, and you want to be able to map how money flows between the different people who use your bank, you might want to map your data as a graph database. That would make it easier to query for the connections across the different users in the bank.
CosmosDB is a database from Microsoft that allows for multiple data models and multiple well-defined consistency models. Today’s guest Andy Hoh is a product manager at Azure CosmosDB and he joins the show to describe the product.
Microsoft unveiled CosmosDB at Build, their annual developer conference, which is where I performed this interview. It was a pleasure hanging out at Build in the podcast booths they set up, so thanks to Microsoft for inviting me.
Transcript provided by We Edit Podcasts. Software Engineering Daily listeners can go to weeditpodcasts.com/sed to get 20% off the first two months of audio editing and transcription services. Thanks to We Edit Podcasts for partnering with SE Daily. Please click here to view this show’s transcript.
Pingback: Dew Drop - June 1, 2017 (#2491) - Morning Dew()
Pingback: TIL #154: Azure Cosmos DB – Jason Neal's Blog()