Kafka, Schema Registry and Avro guide #16503
Conversation
michalszynkiewicz
force-pushed
the
avro-schema-guide
branch
from
98d3cf1 to
5f4128e
Compare
|
corresponding quickstart: quarkusio/quarkus-quickstarts#832 |
|
@Ladicek maybe you'd also like to take a look? |
|
I wanted to check whether we have documentation for Avro, so this is just in time! Too bad Apicurio Registry 2.x isn't out yet -- its Avro library is a little better (or maybe a lot better, I don't know). I'm adding support for that in #16473. |
michalszynkiewicz
force-pushed
the
avro-schema-guide
branch
from
5f4128e to
f53668b
Compare
michalszynkiewicz
force-pushed
the
avro-schema-guide
branch
from
f53668b to
cd0d645
Compare
|
Don't forget to add the guide into the list of guides. |
|
|
||
| == The infrastructure | ||
| To use our application, we need Kafka and Apicurio Schema Registry. | ||
| The easiest way to get them running is to use `docker-compose` to start the appropriate containers. |
There was a problem hiding this comment.
Here is a tricky part... docker-compose became docker compose in the last docker version. I would keep it like this for now, but we may have to update (globally) the reference.
michalszynkiewicz
force-pushed
the
avro-schema-guide
branch
from
cd0d645 to
1c4f914
Compare
|
Before merging, add the guide to the guide list. |
|
|
Thanks! |
| registry = new GenericContainer<>("apicurio/apicurio-registry-mem:1.2.2.Final") | ||
| .withExposedPorts(8080) | ||
| .withEnv("QUARKUS_PROFILE", "prod") | ||
| .withEnv("KAFKA_BOOTSTRAP_SERVERS", kafka.getBootstrapServers()) |
There was a problem hiding this comment.
the env vars KAFKA_BOOTSTRAP_SERVERS , APPLICATION_ID and APPLICATION_SERVER are not required, the image apicurio/apicurio-registry-mem stores the schemas in-memory and do not require access to kafka
There was a problem hiding this comment.
Good point. I'm updating the guide to use Apicurio Registry 2.0.0, so I'll remove this as part of the work.
No description provided.