Azure / Azure/Integration-Services-Landing-Zone-Accelerator
Pattern: Generic Batching and DeBatching
- Dominant language
- Bicep
- Stars
- 68
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
While we have EDI batching... so of, there are other scenarios where we need to batch and debatch messages. Need to have a pattern than makes this simple to implement, track, and manage for our customers.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by clarifying which non-EDI batching and debatching scenarios are supported, how messages should be tracked, and what customer management means; then locate the relevant accelerator entry points. Done should be a documented, agreed pattern with clear implementation and validation requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100