IGNITE-15238 Add a reference on data partitioning deep-dive documentation (#9295)
diff --git a/docs/_docs/data-modeling/data-partitioning.adoc b/docs/_docs/data-modeling/data-partitioning.adoc
index 633b1d2..37432e7 100644
--- a/docs/_docs/data-modeling/data-partitioning.adoc
+++ b/docs/_docs/data-modeling/data-partitioning.adoc
@@ -29,6 +29,8 @@
The affinity key can be any field of the objects stored in the cache (any column in the SQL table).
If the affinity key is not specified, the default key is used (in case of SQL tables, it is the PRIMARY KEY column).
+NOTE: For more information on data partitioning, see the advanced link:https://www.gridgain.com/resources/blog/data-distribution-in-apache-ignite[deep-dive on data partitioning,window=_blank] in Ignite.
+
Partitioning boosts performance by distributing both read and write operations.
Moreover, you can design your data model in such a way that the data entries that are used together are stored together (i.e., in one partition).
When you request that data, only a small number of partitions is scanned.
