From SQL to Azure Cosmos DB
summary
A manufacturing system moves from SQL Server to MongoDB then to Azure Cosmos DB to avoid expensive licenses and VMs, using the Mongo and SQL APIs and the Cosmos data explorer. Documents store denormalized order snapshots (product name, price) and inventory updates happen via outbox/inbox domain events rather than cross-document transactions or server-side JavaScript procedures. Demo e-commerce code shows orders created, approval flips status, and stock decrements asynchronously; the migration succeeds and reduces operational cost and DBA friction.
AI-written summary · about
chapters (23)
- 0:00Intro
- 3:04What is Cosmos DB
- 6:47Why Cosmos DB
- 9:09Schemaless Data
- 11:55Modeling Data
- 19:27Transactional vs Sequel
- 20:04Transaction Support
- 23:02Distributed Transactions
- 26:50Domain Events
- 29:08Serializable
- 30:16Guaranteed
- 33:20Emulator
- 34:35Catalog
- 35:06Cart
- 35:37Code
- 41:34Data Explorer
- 44:02Order Status
- 45:44Existing Documents
- 46:22Document Migration
- 48:08Transactions
- 49:31Order Request
- 52:57Update Failure
- 54:49Publishing Domain Events
related talks
01h 01mFrom SQL to Azure Cosmos DB
18mNoSQL, YesCosmos: Build that Eventually Consistent Application using Azure Cosmos DB
03h 30mAmericas Live Stream
20mHow Azure Cosmos DB enables Event Sourcing architecture
01h 01mServerless & Schemaless with Azure Functions and CosmosDB
20mHow Azure Cosmos DB enables Event Sourcing architecture and powers e-commerce
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
52mEvent journal in Azure (no Cosmos inside)