anchor.diff:      If it were the case, instantiating a consumer would be useless.
   . We have to open two connections, and repeat twice the connection settings like `bootstrap.servers`,
       once for the admin client, then for the consumer client.
  -    It would be interesting if they could share options and may be even the TCP connection.
  +    It would be interesting if they could share options and maybe even the TCP connection.
   . `AdminClient` class often returns `KafkaFuture<Something>`,
       the API design is very different from `Consumer` and `Producer` clients.
       I wonder why they created a `KafkaFuture` class instead of reusing `CompletableFuture`.
  
positive.code: :page-description: "How to retrieve Kafka consumer lag with Java API."
  
  This article shows how to get Kafka lag for a given consumer group using the Java API.
  It's about implementing part of the `kafka-consumer-group` command line tool in pure Java.
  
  image::{imagedir}/lag.svg[Consumer Lag]
  
  
negative.code: 
  Kafka 2.0 introduced an `AdminClient` class which contains a very useful
  https://kafka.apache.org/20/javadoc/org/apache/kafka/clients/admin/AdminClient.html#listConsumerGroupOffsets-java.lang.String-org.apache.kafka.clients.admin.ListConsumerGroupOffsetsOptions-[listConsumerGroupOffsets] method.
  This method returns for a given consumer group a dictionary _(topic name, partition) -> current offset_
  
  [source, java]
  ----
  