--- title: Salesforce Engineering: Global Synchronousness and... description: Salesforce engineering describes a production issue with Delta Lake where multiple concurrent write streams to the same table frequently caused Conflicting... canonical: https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Salesforce Engineering: Global Synchronousness and Ordering in Delta Lake | daily.dev og:description: Salesforce engineering describes a production issue with Delta Lake where multiple concurrent write streams to the same table frequently caused Conflicting... og:url: https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci og:image: https://api.daily.dev/og/posts/w184aaccI.png og:image:alt: Salesforce Engineering: Global Synchronousness and Ordering in Delta Lake 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. # Salesforce Engineering: Global Synchronousness and Ordering in Delta Lake **[Delta Lake Blog](https://daily.dev/sources/delta-lake)** · 2 min read · 0 upvotes · 0 comments ## Summary Salesforce engineering describes a production issue with Delta Lake where multiple concurrent write streams to the same table frequently caused Conflicting Commits errors, despite Delta Lake's ACID transaction guarantees maintaining data integrity. The team built a mechanism to enforce global synchronousness and ordering across concurrent writers, eliminating these conflicts and improving pipeline stability for their customer activity data lake powering Einstein Analytics dashboards and ML models. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do I keep getting Conflicting Commits errors when multiple streams write to the same Delta Lake table? Delta Lake's ACID transactions guarantee data integrity but provide no built-in mechanism to resolve write conflicts between independent concurrent writers, so multiple streams modifying the same table frequently trigger Conflicting Commits errors that fail the pipeline. Salesforce engineering solved this by enforcing global synchronousness and ordering across all writers to the shared table, eliminating the errors while preserving data integrity. _daily.dev surfaces engineering writeups like this for teams debugging Delta Lake write conflicts in production._ ## Similar posts on daily.dev - [Delta Lake Explained: Boost Data Reliability in Cloud Storage](https://daily.dev/posts/delta-lake-explained-boost-data-reliability-in-cloud-storage-oechbmvm4) · databricks · 0 upvotes · 0 comments - [Confluent Tableflow \+ Databricks Unity Catalog](https://daily.dev/posts/confluent-tableflow-databricks-unity-catalog-3l7atiiei) · Confluent Blog · 1 upvotes · 0 comments - [Building a Multi Region Compliant Customer Data Lake at Scale](https://daily.dev/posts/building-a-multi-region-compliant-customer-data-lake-at-scale-pwe2wnx7k) · Atlassian · 0 upvotes · 0 comments - [Building a Database on S3](https://daily.dev/posts/building-a-database-on-s3-z6q1mg0wr) · Metadata · 47 upvotes · 0 comments - [Data Versioning in Machine Learning and Data Lakes](https://daily.dev/posts/data-versioning-in-machine-learning-and-data-lakes-znyfovuze) · Medium · 0 upvotes · 0 comments --- Tags: [#data-engineering](https://daily.dev/tags/data-engineering), [#apache-spark](https://daily.dev/tags/apache-spark) [View this post on daily.dev](https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci) ```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":"Salesforce Engineering: Global Synchronousness and Ordering in Delta Lake","url":"https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci"},"datePublished":"2026-08-16T08:53:52.024Z","dateModified":"2026-08-16T08:56:28.348Z","description":"Salesforce engineering describes a production issue with Delta Lake where multiple concurrent write streams to the same table frequently caused Conflicting...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/57976a9b4c375a0db616eb1532fba299?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/57976a9b4c375a0db616eb1532fba299?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Delta Lake Blog","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":"Delta Lake Blog","logo":"https://media.daily.dev/image/upload/s--7f2q9Asf--/f_auto,q_auto/v1786870393/logos/delta-lake?_a=BAMAMicg0","url":"https://daily.dev/sources/delta-lake"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"data-engineering,apache-spark","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Delta Lake Blog","item":"https://daily.dev/sources/delta-lake"},{"@type":"ListItem","position":3,"name":"Salesforce Engineering: Global Synchronousness and Ordering in Delta Lake"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/salesforce-engineering-global-synchronousness-and-ordering-in-delta-lake-w184aacci#faq","mainEntity":[{"@type":"Question","name":"Why do I keep getting Conflicting Commits errors when multiple streams write to the same Delta Lake table?","acceptedAnswer":{"@type":"Answer","text":"Delta Lake's ACID transactions guarantee data integrity but provide no built-in mechanism to resolve write conflicts between independent concurrent writers, so multiple streams modifying the same table frequently trigger Conflicting Commits errors that fail the pipeline. Salesforce engineering solved this by enforcing global synchronousness and ordering across all writers to the shared table, eliminating the errors while preserving data integrity. daily.dev surfaces engineering writeups like this for teams debugging Delta Lake write conflicts in production."}}]} ```