Azure Cosmos DB is rapidly becoming a household name in data management among developers, though its change feed is still considered somewhat of an unsung facet to its operational capability. In this Microsoft Blog post, Tallan Principal Consultant Leonard Lobel discusses multiple scenarios that call upon the need for a change feed as they relate to varying documents in a container. These scenarios include:
- Replicating containers for multiple partition keys
- Denormalizing a document data model across containers
- Triggering API calls for an event-driven architecture
- Real time stream processing and materialized view patterns
- Moving or archiving data to secondary data stores
Leonard Lobel (Microsoft MVP, SQL Server) is the chief technology officer and co-founder of Sleek Technologies, Inc., a New York-based development shop with an early adopter philosophy toward new technologies. He is also a principal consultant at Tallan, Inc., one of only 40 Microsoft National Systems Integrators in the United States. For more than 25 years, Tallan has been providing cutting-edge custom web/application development, business intelligence, customer relationship management, and integration services.Programming since 1979, Lenni specializes in Microsoft-based solutions, with experience that spans a variety of business domains, including publishing, financial, wholesale/retail, health care, and e-commerce. Lenni has served as chief architect and lead developer for various organizations, ranging from small shops to high-profile clients. He is also a consultant, trainer, and frequent speaker at local usergroup meetings, SQL PASS, SQLBits, Visual Studio Live!, and other industry conferences.