Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using external registry for avro or protocol buffers #1010

Open
franciscolopezsancho opened this issue Mar 24, 2021 · 0 comments
Open

Using external registry for avro or protocol buffers #1010

franciscolopezsancho opened this issue Mar 24, 2021 · 0 comments

Comments

@franciscolopezsancho
Copy link
Collaborator

franciscolopezsancho commented Mar 24, 2021

the UX

the developer may want to

  1. create their schema from a local file
  2. consume/update their schema from a registry. It has to be Kafka? https://docs.confluent.io/platform/current/schema-registry/schema_registry_onprem_tutorial.html#auto-schema-registration

Starting with local schemas

  • 1A. When buildApp they might want to
    • 1A.1 upload the schema to registry
    • 1A.2 make sure the schema has no conflict with latest version of uploaded schema. Assuming this will be the version deployed in the cluster.
  • 1B. When deploy app, is it necessary to check? after all has to be done with buildApp. But what about we try to deploy a rollback or anything of that sort. Would be still compatible? I think so

Starting with remote Schemas

  • 2A. When writing the app. So they need a way to download it or should be always part of the source code? tempted for the later to avoid problems.1
  • 2B. When buildApp same as 1A

problems:

  1. if from one workstation that access to the schema uses style 2 and from the next workstation there's no access to the registry -> always add schemas in local?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant