Duplicate Data with BlueGreen Deployment
- Dominant language
- Go
- Stars
- 581
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Our usecase is streaming data from kafka --> processing them in flink --> and saving the data in a database.
With the blue green deployment, i assume while both blue and green are up both would be sending data in my db. Is that correct?
How would you recommend preventing this to happen so my data is still consistent.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are mentioned. Start by reviewing the operator's blue-green deployment behavior for Kafka-to-Flink-to-database workloads, then document whether both deployments can write concurrently and what consistency-preserving approach is recommended. Done means the deployment behavior and prevention guidance are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, kubernetes
- Domain
- databases, distributed-systems, infrastructure, stream-processing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100