Add figure for SAC + super stream

References #46

Author: acogoluegnes

pom.xml

@@ -417,22 +417,22 @@
 
         </configuration>
         <executions>
-          <execution>
-            <id>generate-pdf</id>
-            <phase>pre-site</phase>
-            <goals>
-              <goal>process-asciidoc</goal>
-            </goals>
-            <configuration>
-              <backend>pdf</backend>
-              <attributes>
-                <title-page />
-                <toc />
-                <toclevels>4</toclevels>
-                <pagenums />
-              </attributes>
-            </configuration>
-          </execution>
+<!--          <execution>-->
+<!--            <id>generate-pdf</id>-->
+<!--            <phase>pre-site</phase>-->
+<!--            <goals>-->
+<!--              <goal>process-asciidoc</goal>-->
+<!--            </goals>-->
+<!--            <configuration>-->
+<!--              <backend>pdf</backend>-->
+<!--              <attributes>-->
+<!--                <title-page />-->
+<!--                <toc />-->
+<!--                <toclevels>4</toclevels>-->
+<!--                <pagenums />-->
+<!--              </attributes>-->
+<!--            </configuration>-->
+<!--          </execution>-->
           <execution>
             <id>generate-html</id>
             <phase>pre-site</phase>

src/docs/asciidoc/super-streams.adoc

@@ -233,7 +233,36 @@ Such a super stream consumer is a _composite consumer_.
 So among these 9 consumer instances, only 3 are actually _active_, the other ones are idle or _inactive_.
 * If one of the application instances stops, the broker will _rebalance_ its active consumer to one of the other instances.
 
-The following figure illustrates how the consumer instances spread across the super stream partitions and which ones are active or inactive:
+The following figure illustrates how the client library supports the combination of the super stream and single active consumer features.
+It uses a composite consumer that creates an individual consumer for each partition of the super stream.
+If there is only one single active consumer instance with a given name for a super stream, each individual consumer is active.
+
+.A single active consumer on a super stream is a composite consumer that creates an individual consumer for each partition
+[ditaa]
+....
+              +--------------------+
+              |                    |
+              |cGRE invoices–0     |
+              |                    |    +-------------------+
+              +--------------------+    |+-----------------+|
+                                        |+cGRE consumer    ||Active
+                                        |+-----------------+|
+  invoices    +--------------------+    |                   |
+              |                    |    |+-----------------+|
+              |cPNK invoices–1     |    |+cPNK consumer    ||Active
+              |                    |    |+-----------------+|
+super stream  +--------------------+    |                   |
+                                        |+-----------------+|
+                                        |+cBLU consumer    ||Active
+              +--------------------+    |+-----------------+|
+              |                    |    +-------------------+
+              |cBLU invoices–2     |     Composite Consumer
+              |                    |
+              +--------------------+
+....
+
+Imagine now we start 3 instances of the consuming application to scale out the processing.
+The individual consumer instances spread out across the super stream partitions and only one is active for each partition, as illustrated in the following figure:
 
 .Consumer instances spread across the super stream partitions and are activated accordingly
 [ditaa]