cancel
Showing results for 
Search instead for 
Did you mean: 
Community Articles
Dive into a collaborative space where members like YOU can exchange knowledge, tips, and best practices. Join the conversation today and unlock a wealth of collective wisdom to enhance your experience and drive success.
cancel
Showing results for 
Search instead for 
Did you mean: 

Forum Posts

Gaurav11
by New Contributor III
  • 282 Views
  • 2 replies
  • 1 kudos

Building a Large-Scale Supply Chain Simulation Platform on Databricks

A Data & AI–Driven Decision Engine for Modern Retail NetworksIntroductionIn modern retail, supply chains are no longer static networks — they are living, adaptive systems that must continuously respond to customer demand, fulfillment speed expectatio...

  • 282 Views
  • 2 replies
  • 1 kudos
Latest Reply
StaniGora
Visitor
  • 1 kudos

Great article! would love to know more as I have a very similar case with a concrete customer. Thanks, S. 

  • 1 kudos
1 More Replies
Gaurav11
by New Contributor III
  • 284 Views
  • 1 replies
  • 3 kudos

Secure Credit Card Partner Enablement Using Databricks Clean Rooms

How Digital Payment Lending Platforms Can Collaborate with Banks Without Exposing Sensitive Data1. Business Context & Regulatory RealityIn 2020, large Indian fintech platforms faced a unique regulatory constraint: NBFC‑led digital platforms were not ...

  • 284 Views
  • 1 replies
  • 3 kudos
Latest Reply
marthala
New Contributor II
  • 3 kudos

This is a solid breakdown of how secure data collaboration can be done without exposing sensitive information. The Clean Room approach really stands out because it shifts the model from data sharing to controlled computation, which is exactly what re...

  • 3 kudos
Ashwin_DSA
by Databricks Employee
  • 447 Views
  • 2 replies
  • 7 kudos

Databricks Multi-Table Transactions - Part 1

If you've ever worked on an insurance data warehouse, or really any warehouse where data arrives from different systems at different times, you know the pain of keeping things in sync. I spent years building data warehouses for a property and casual...

claim-wrapup-flow.png before-after-transactions.png Part1 Cover Pic.png
  • 447 Views
  • 2 replies
  • 7 kudos
Latest Reply
Louis_Frolio
Databricks Employee
  • 7 kudos

This is a great write piece @Ashwin_DSA 

  • 7 kudos
1 More Replies
mderela
by Contributor
  • 209 Views
  • 0 replies
  • 1 kudos

𝗦𝗜𝗘𝗠 𝗶𝘀 𝗹𝗲𝗴𝗮𝗰𝘆. Here's why, and what becomes possible when you move security operations

I've spent years migrating SOC operations from traditional SIEM to Databricks. Not because it's trendy, but because SIEM has fundamental problems that no vendor update will fix: proprietary query languages that lock you in, no version control or test...

  • 209 Views
  • 0 replies
  • 1 kudos
Kirankumarbs
by Contributor
  • 475 Views
  • 9 replies
  • 6 kudos

Streaming Failure Models: Why "It Didn't Crash" Is the Worst Outcome

Most Databricks streaming failures don't look dramatic.No cluster termination. No red wall of errors. The UI says RUNNING — and your customers start reporting nonsense.I wrote about the incident that changed how we think about streaming jobs on share...

  • 475 Views
  • 9 replies
  • 6 kudos
Latest Reply
mderela
Contributor
  • 6 kudos

Completely agree, production war stories are worth more than any documentation. I’ve eaten enough teeth on production data lake issues to write my own chapter on what can go wrong, whether that’s deploying Databricks in financial institutions or bein...

  • 6 kudos
8 More Replies
Kirankumarbs
by Contributor
  • 258 Views
  • 1 replies
  • 2 kudos

Multi-Task on a Shared Cluster — Why That's Also Not Enough

Part 2 of 3 — Databricks Streaming ArchitectureThe instinct after Part 1 was obvious.If running eight queries in one task means one failure can hide while others keep running — split them into multiple tasks. Separate concerns. Give each component it...

  • 258 Views
  • 1 replies
  • 2 kudos
Latest Reply
Kirankumarbs
Contributor
  • 2 kudos

Part 1: Streaming Failure Models: Why "It Didn't Crash" Is the Worst OutcomePart 3: One Cluster per Task — Proven, Ready, and Waiting

  • 2 kudos
Kirankumarbs
by Contributor
  • 155 Views
  • 0 replies
  • 1 kudos

One Cluster per Task — Proven, Ready, and Waiting

Part 3 of 3: Databricks Streaming ArchitectureBy the end of Part 1 & Part 2, we knew what the real answer was. We just hadn’t committed to it yet.Not because it wouldn’t work. We tested it. We documented it. The code was ready. The answer was one clu...

  • 155 Views
  • 0 replies
  • 1 kudos
Labels