Skip to content

Commit 6de1379

Browse files
authored
Update index.md
1 parent 98df28a commit 6de1379

1 file changed

Lines changed: 1 addition & 18 deletions

File tree

blog/batch-vs-stream-processing/index.md

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -53,23 +53,6 @@ Six months later, I had learned more about the real cost of streaming than any b
5353
This is that story — and the honest breakdown I wish someone had given me before I started.
5454

5555

56-
## What Nobody Tells You Before You Go Streaming
57-
58-
The conversation around streaming pipelines almost always focuses on the benefits:
59-
60-
- 1. Real-time insights
61-
- 2. Millisecond latency
62-
- 3. Event-driven reactions
63-
- 4. Live personalization
64-
- 5. Fraud detection before transactions complete
65-
66-
All of that is true. Streaming genuinely enables things batch never could.
67-
68-
But the conversation stops there. Nobody walks you through what you're signing up for on the other side of that decision.
69-
70-
Let me do that.
71-
72-
7356
## What We Had Before (And Why It Worked)
7457

7558
Our original order pipeline was batch. It ran every night at 2am via Azure Data Factory, pulled 24 hours of orders from our SQL database, ran a Spark transformation job, and wrote clean Delta tables to ADLS Gen2.
@@ -281,4 +264,4 @@ I'm **Aditya Singh Rathore**, a Data Engineer passionate about building modern,
281264

282265
📩 Have you been burned by a streaming pipeline that didn't need to be? Drop it in the comments.
283266

284-
<GiscusComments/>
267+
<GiscusComments/>

0 commit comments

Comments
 (0)