add information about parallel replicas

Author: Blargian

docs/data-modeling/projections/2_materialized-views-versus-projections.md

@@ -28,6 +28,7 @@ The table below summarizes the key differences between materialized views and pr
 | Operational overhead         | Requires explicit target table creation and often manual backfilling. Managing consistency with `UPDATE`/`DELETE` increases complexity.                                                                                                                                                                                                                                   | Projections are automatically maintained and kept-in-sync and generally have a lower operational burden.                                                                                                                                                                                               |
 | `FINAL` query compatibility  | Generally compatible, but often require `GROUP BY` on the target table.                                                                                                                                                                                                                                                                                                   | **Do not work** with `FINAL` queries.                                                                                                                                                                                                                                                                  |
 | Lazy materialization         | Yes.                                                                                                                                                                                                                                                                                                                                                                      | Monitor for projection compatibility issues when using materialization features. You may need to set `query_plan_optimize_lazy_materialization = false`                                                                                                                                                |
+| Parallel replicas            | Yes.                                                                                                                                                                                                                                                                                                                                                                      | No.                                                                                                                                                                                                                                                                                                    |
 
 ## Comparing materialized views and projections {#choose-between}
 
@@ -62,7 +63,7 @@ You should consider avoiding the use of projections when:
 - **Explicit filtering of materialized data is needed**: Projections do not support `WHERE` clauses in their definition to filter the data that gets materialized into the projection itself.
 - **Non-MergeTree table engines are used**: Projections are exclusively available for tables using the `MergeTree` family of engines.
 - `FINAL` queries are essential: Projections do not work with `FINAL` queries, which are sometimes used for deduplication.
-- Working with large tables that grow quickly: 
+- You need [parallel replicas](/deployment-guides/parallel-replicas) as they are not supported with projections.
 
 ## Summary {#summary}