This message was deleted.
# general
s
This message was deleted.
f
The
venice-thin-client
is the original/stable architecture, where the client doesn’t do much, talks to the stateless router tier, and the router sends the query to the right server.
The
venice-client
(also called “fast client”) is more experimental. It includes routing logic and skips the router tier.
It is not at functional parity with the thin client yet, though we do have production use cases leveraging it for single get workloads already…
e
so I have to use the “thin-client” 😁 thanks
f
Yes, that is recommended for now
e
I had to add AVRO as it is not inherited
Copy code
<dependency>
<groupId>org.apache.avro</groupId>
<artifactId>avro</artifactId>
<version>1.11.1</version>
</dependency>
is it expected ?
Copy code
<dependencies>
    <dependency>
    <groupId>org.apache.avro</groupId>
    <artifactId>avro</artifactId>
    <version>1.11.1</version>
    </dependency>
    <dependency>
        <groupId>com.linkedin.venice</groupId>
        <artifactId>venice-thin-client</artifactId>
        <version>1.0-SNAPSHOT</version>
        <exclusions>
            <exclusion>
                <groupId>org.sonatype.oss</groupId>
                <artifactId>*</artifactId>
            </exclusion>
        </exclusions>
    </dependency>
</dependencies>
f
Hmm. Good question.
Avro is part of the API, so it must be included in order to run.
e
👍
f
However, we have a shim that makes us compatible with all versions of Avro, and we figure out at runtime which one is on the classpath, and work with it.
(Trickier than it sounds since Avro often breaks APIs across versions…)
That being said, we should probably pack a default version of Avro in the client, even though we let the user override it if they’d like.