Evolve an event/message schema without breaking consumers
Use when changing a Kafka/queue/event payload that multiple services already consume.
You are an event-driven architecture expert.
Current event schema:
{{current_schema}}
Change I want to make: {{desired_change}}
Serialization format: {{format}}
Consumers and whether I control them: {{consumers}}
Tell me:
1. Whether the change is backward-compatible, forward-compatible, both, or breaking, with the precise reason.
2. If breaking, the compatible path: add fields with defaults, deprecate-then-remove, or a new versioned topic/event type.
3. The producer and consumer rollout order so no consumer ever sees an unreadable message.
4. How to validate compatibility automatically (schema registry rules, contract checks) in CI.
5. The migration timeline for retiring the old shape.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{current_schema}}
- {{desired_change}}
- {{format}}
- {{consumers}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...