--- title: Genspark protects live agent sessions with Azure Cosmos... description: Genspark, an AI agent workspace, describes how it used Azure Cosmos DB Global Secondary Indexes (GSI) to isolate read-heavy internal background workloads from... canonical: https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Genspark protects live agent sessions with Azure Cosmos DB Global Secondary Indexes | daily.dev og:description: Genspark, an AI agent workspace, describes how it used Azure Cosmos DB Global Secondary Indexes (GSI) to isolate read-heavy internal background workloads from... og:url: https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit og:image: https://api.daily.dev/og/posts/nfeJ2KxIT.png og:image:alt: Genspark protects live agent sessions with Azure Cosmos DB Global Secondary Indexes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Genspark protects live agent sessions with Azure Cosmos DB Global Secondary Indexes **[DevBlogs](https://daily.dev/sources/devblogs)** · 5 min read · 1 upvotes · 0 comments ## Summary Genspark, an AI agent workspace, describes how it used Azure Cosmos DB Global Secondary Indexes (GSI) to isolate read-heavy internal background workloads from live agent session traffic. Instead of building a separate replica or ETL pipeline, Genspark routed selected background reads to a GSI that Cosmos DB automatically keeps in sync via change feed. The team evaluated which processes could tolerate eventual consistency versus those needing the freshest state, then migrated the tolerant workloads to the GSI, achieving workload isolation without operating additional infrastructure. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are Azure Cosmos DB Global Secondary Indexes used for? Global Secondary Indexes (GSI) in Azure Cosmos DB provide an additional read path that stays automatically synchronized with a source container via change feed, without requiring a separate replication pipeline. They let teams route read-heavy background workloads away from the capacity serving live reads and writes, while the source container continues to serve the freshest state for latency-sensitive operations. _Developers isolating read-heavy workloads from live traffic can track Cosmos DB architecture patterns like this on daily.dev._ ### How consistent is data in an Azure Cosmos DB global secondary index compared to the source container? A global secondary index in Azure Cosmos DB is eventually consistent with its source container rather than strongly consistent. Teams must evaluate each workload against the question of what breaks if the data is slightly behind, routing only processes that can tolerate a lagging copy to the index while keeping latency-sensitive reads on the source container. _Anyone weighing consistency tradeoffs for a database migration can follow related discussions on daily.dev._ ## Similar posts on daily.dev - [Need a different partition key in Azure Cosmos DB? Pick the right approach](https://daily.dev/posts/need-a-different-partition-key-in-azure-cosmos-db-pick-the-right-approach-sfo1aamze) · DevBlogs · 0 upvotes · 0 comments - [Azure Cosmos DB Agent Skills: Securing Database Access for AI Coding Agents](https://daily.dev/posts/azure-cosmos-db-agent-skills-securing-database-access-for-ai-coding-agents-5nriajmxs) · C\# Corner · 0 upvotes · 0 comments - [How Indra unified EV charging data on Databricks](https://daily.dev/posts/how-indra-unified-ev-charging-data-on-databricks-2q57g75i9) · databricks · 0 upvotes · 0 comments - [The power of multi-model Spanner for the agentic era](https://daily.dev/posts/the-power-of-multi-model-spanner-for-the-agentic-era-qdwjuy0cw) · Google Cloud · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#architecture](https://daily.dev/tags/architecture), [#database](https://daily.dev/tags/database), [#azure-cosmos-db](https://daily.dev/tags/azure-cosmos-db) [View this post on daily.dev](https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Genspark protects live agent sessions with Azure Cosmos DB Global Secondary Indexes","url":"https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit"},"datePublished":"2026-10-01T16:03:43.210Z","dateModified":"2026-10-01T16:04:30.424Z","description":"Genspark, an AI agent workspace, describes how it used Azure Cosmos DB Global Secondary Indexes (GSI) to isolate read-heavy internal background workloads from...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c52484201615a9d3b8e4dafef7807c87?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c52484201615a9d3b8e4dafef7807c87?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DevBlogs","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DevBlogs","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8f68b453325f482ebeb73fb780092713","url":"https://daily.dev/sources/devblogs"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,architecture,database,azure-cosmos-db","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevBlogs","item":"https://daily.dev/sources/devblogs"},{"@type":"ListItem","position":3,"name":"Genspark protects live agent sessions with Azure Cosmos DB Global Secondary Indexes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/genspark-protects-live-agent-sessions-with-azure-cosmos-db-global-secondary-indexes-nfej2kxit#faq","mainEntity":[{"@type":"Question","name":"What are Azure Cosmos DB Global Secondary Indexes used for?","acceptedAnswer":{"@type":"Answer","text":"Global Secondary Indexes (GSI) in Azure Cosmos DB provide an additional read path that stays automatically synchronized with a source container via change feed, without requiring a separate replication pipeline. They let teams route read-heavy background workloads away from the capacity serving live reads and writes, while the source container continues to serve the freshest state for latency-sensitive operations. Developers isolating read-heavy workloads from live traffic can track Cosmos DB architecture patterns like this on daily.dev."}},{"@type":"Question","name":"How consistent is data in an Azure Cosmos DB global secondary index compared to the source container?","acceptedAnswer":{"@type":"Answer","text":"A global secondary index in Azure Cosmos DB is eventually consistent with its source container rather than strongly consistent. Teams must evaluate each workload against the question of what breaks if the data is slightly behind, routing only processes that can tolerate a lagging copy to the index while keeping latency-sensitive reads on the source container. Anyone weighing consistency tradeoffs for a database migration can follow related discussions on daily.dev."}}]} ```