docarray
diff --git a/Collapse file
‎docs/advanced/document-store/index.md‎
Copy file name to clipboardExpand all lines: docs/advanced/document-store/index.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff b/Collapse file
‎docs/advanced/document-store/index.md‎
Copy file name to clipboardExpand all lines: docs/advanced/document-store/index.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
@@ -151,15 +151,19 @@ Using dataclass gives you better type-checking in IDE but requires an extra impo
 DocArray supports multiple storage backends with different search features. The following table showcases relevant functionalities that are supported (✅) or not supported (❌) in DocArray depending on the backend:
 
 
-| Name                                 | Construction                             |  vector search | vector search + filter | filter|
-|--------------------------------------|------------------------------------------|---------------|------------------------|---------------|
-| In memory                            | `DocumentArray()`                        | ✅             | ✅                      | ✅             |
-| [`Sqlite`](./sqlite.md)              | `DocumentArray(storage='sqlite')`        | ❌             | ❌                      | ✅             | 
-| [`Weaviate`](./weaviate.md)          | `DocumentArray(storage='weaviate')`      | ✅             | ✅                      | ✅             |
-| [`Qdrant`](./qdrant.md)              | `DocumentArray(storage='qdrant')`        | ✅             | ✅                      | ❌             |
-| [`Annlite`](./annlite.md)            | `DocumentArray(storage='annlite')`       | ✅             | ✅                      | ✅             |
-| [`ElasticSearch`](./elasticsearch.md) | `DocumentArray(storage='elasticsearch')` | ✅             | ✅                      | ✅             |
-| [`Redis`](./redis.md)                | `DocumentArray(storage='redis')`         | ✅             | ✅                      | ✅             |
+| Name                                  | Construction                             |  vector search | vector search + filter | filter        |
+|---------------------------------------|------------------------------------------|----------------|------------------------|---------------|
+| In memory                             | `DocumentArray()`                        | ✅             | ✅                     | ✅            |
+| [`Sqlite`](./sqlite.md)               | `DocumentArray(storage='sqlite')`        | ❌             | ❌                     | ✅            | 
+| [`Weaviate`](./weaviate.md)           | `DocumentArray(storage='weaviate')`      | ✅             | ✅                     | ✅            |
+| [`Qdrant`](./qdrant.md)               | `DocumentArray(storage='qdrant')`        | ✅             | ✅                     | ❌            |
+| [`AnnLite`](./annlite.md)             | `DocumentArray(storage='annlite')`       | ✅             | ✅                     | ✅            |
+| [`ElasticSearch`](./elasticsearch.md) | `DocumentArray(storage='elasticsearch')` | ✅             | ✅                     | ✅            |
+| [`Redis`](./redis.md)                 | `DocumentArray(storage='redis')`         | ✅             | ✅                     | ✅            |
+
+The right backend choice depends on the scale of your data, the required performance and the desired ease of setup. For most use cases we recommend starting with [`AnnLite`](./annlite.md).
+[**Check our One Million Scale Benchmark for more details**](./benchmark#conclusion).
+
 
 
 Here we understand by 
@@ -170,10 +174,9 @@ Here we understand by
 
 - **filter**: perform a filter step over the data. The input of the search function is a filter. 
 
-The capabilities of  **vector search**,  **vector search + filter** can be used using the  {meth}`~docarray.array.mixins.find.FindMixin.find` or {func}`~docarray.array.mixins.match.MatchMixin.match` methods thorugh a  `DocumentArray`.
+The capabilities of  **vector search**,  **vector search + filter** can be used using the  {meth}`~docarray.array.mixins.find.FindMixin.find` or {func}`~docarray.array.mixins.match.MatchMixin.match` methods through a  `DocumentArray`.
 The **filter** functionality is available using the `.find` method in a `DocumentArray`. 
-A detailed explanation of the differences between `.find` and `.match` can be found [`here`](./../../../fundamentals/documentarray/matching) 
-
+A detailed explanation of the differences between `.find` and `.match` can be found [here](./../../../fundamentals/documentarray/matching) 
 
 ### Vector search example