YDBDOCS-633: continue restructuring (#4036)

Author: blinkov

ydb/docs/en/core/changelog-cli.md

@@ -137,7 +137,7 @@ Release date: May 1, 2023. To update to version **2.3.0**, select the [Downloads
 **Features:**
 
 * Added the interactive mode of query execution. To switch to the interactive mode, run [ydb yql](reference/ydb-cli/yql.md) without arguments. This mode is experimental: backward compatibility is not guaranteed yet.
-* Added the [ydb index rename](reference/ydb-cli/commands/secondary_index.md#rename) command for [atomic replacement](dba/secondary-indexes.md#atomic-index-replacement) or renaming of a secondary index.
+* Added the [ydb index rename](reference/ydb-cli/commands/secondary_index.md#rename) command for [atomic replacement](dev/secondary-indexes.md#atomic-index-replacement) or renaming of a secondary index.
 * Added the `ydb workload topic` command for generating the load that reads messages from topics and writes messages to topics.
 * Added the [--recursive](reference/ydb-cli/commands/dir.md#rmdir-options) option for the `ydb scheme rmdir` command. Use it to delete a directory recursively, with all its content.
 * Added support for the `topic` and `coordination node` types in the [ydb scheme describe](reference/ydb-cli/commands/scheme-describe.md) command.

ydb/docs/en/core/changelog-server.md

@@ -154,7 +154,7 @@ Release date: May 5, 2023. To update to version 23.1, select the [Downloads](dow
 **Functionality:**
 
 * Added [initial table scan](concepts/cdc.md#initial-scan) when creating a CDC changefeed. Now, you can export all the data existing at the time of changefeed creation.
-* Added [atomic index replacement](dba/secondary-indexes.md#atomic-index-replacement). Now, you can atomically replace one pre-defined index with another. This operation is absolutely transparent for your application. Indexes are replaced seamlessly, with no downtime.
+* Added [atomic index replacement](dev/secondary-indexes.md#atomic-index-replacement). Now, you can atomically replace one pre-defined index with another. This operation is absolutely transparent for your application. Indexes are replaced seamlessly, with no downtime.
 * Added the [audit log](security/audit-log.md): Event stream including data about all the operations on {{ ydb-short-name }} objects.
 
 **Performance:**

ydb/docs/en/core/concepts/_includes/scan_query.md

@@ -11,7 +11,7 @@ This method of executing queries has the following unique features:
 
 {% node info %}
 
-From the *Scan Queries* interface, you can query [system tables](../../dba/system-views.md).
+From the *Scan Queries* interface, you can query [system tables](../../dev/system-views.md).
 
 {% endnote %}
 

ydb/docs/en/core/concepts/_includes/secondary_indexes.md

@@ -59,5 +59,5 @@ A secondary index can be:
 
 ## Purpose and use of secondary indexes {#best_practices}
 
-For information about the purpose and use of secondary indexes for app development, see the [recommendations](../../dba/secondary-indexes.md).
+For information about the purpose and use of secondary indexes for app development, see the [recommendations](../../dev/secondary-indexes.md).
 

ydb/docs/en/core/concepts/cdc.md

@@ -243,4 +243,4 @@ You can add a changefeed to an existing table or erase it using the [ADD CHANGEF
 
 ## CDC purpose and use {#best_practices}
 
-For information about using CDC when developing apps, see [best practices](../dba/cdc.md).
+For information about using CDC when developing apps, see [best practices](../dev/cdc.md).

ydb/docs/en/core/concepts/datamodel/_includes/table.md

@@ -28,7 +28,7 @@ Searching using an index allows you to swiftly locate the required rows without
 
 You can create a row-oriented table through the YDB web interface, CLI, or SDK. Regardless of the method you choose to interact with YDB, it's important to keep in mind the following rule: the table must have at least one primary key column, and it's permissible to create a table consisting solely of primary key columns.
 
-By default, when creating a row-oriented table, all columns are optional and can have `NULL` values. This behavior can be modified by setting the `NOT NULL` conditions for key columns that are part of the primary key. Primary keys are unique, and row-oriented tables are always sorted by this key. This means that point reads by the key, as well as range queries by key or key prefix, are efficiently executed (essentially using an index). It's permissible to create a table consisting solely of key columns. When choosing a key, it's crucial to be careful, so we recommend reviewing the article: ["Choosing a Primary Key for Maximum Performance"](../../../dba/primary-key/row-oriented.md).
+By default, when creating a row-oriented table, all columns are optional and can have `NULL` values. This behavior can be modified by setting the `NOT NULL` conditions for key columns that are part of the primary key. Primary keys are unique, and row-oriented tables are always sorted by this key. This means that point reads by the key, as well as range queries by key or key prefix, are efficiently executed (essentially using an index). It's permissible to create a table consisting solely of key columns. When choosing a key, it's crucial to be careful, so we recommend reviewing the article: ["Choosing a Primary Key for Maximum Performance"](../../../dev/primary-key/row-oriented.md).
 
 ### Partitioning row-oriented tables {#partitioning}
 
@@ -221,7 +221,7 @@ WITH (STORE = COLUMN);
 Unlike data partitioning in row-oriented {{ ydb-short-name }} tables, key values are not used to partition data in column-oriented tables. This way, you can uniformly distribute data across all your existing partitions. This kind of partitioning enables you to avoid hotspots at data inserta and speeding up analytical queries that process (that is, read) large amounts of data.
 
 
-How you select partitioning keys substantially affects the performance of queries to your column-oriented tables. Learn more in [{#T}](../../../dba/primary-key/column-oriented.md).
+How you select partitioning keys substantially affects the performance of queries to your column-oriented tables. Learn more in [{#T}](../../../dev/primary-key/column-oriented.md).
 
 To manage data partitioning, use the `AUTO_PARTITIONING_MIN_PARTITIONS_COUNT` additional parameter. The system ignores other partitioning parameters for column-oriented tables.
 

ydb/docs/en/core/dba/index.md

@@ -2,7 +2,7 @@
 
 First of all, you'll need to obtain access to a {{ ydb-short-name }} cluster. Follow the [quickstart instructions](../quickstart.md) to get a basic local instance. Later on, you can work with your DevOps team to [build a production-ready cluster](../devops/index.md) or leverage one of the cloud service providers that offer a managed {{ ydb-short-name }} service.
 
-The second step is designing a data schema for an application you will build from scratch or adapt the schema of an existing application if you're migrating from another database management system. Work with your DBA on this, or refer to the documentation [for DBA](../dba/index.md) yourself if you don't have one on your team.
+The second step is designing a data schema for an application you will build from scratch or adapt the schema of an existing application if you're migrating from another database management system. Work with your DBA on this, or refer to the documentation [for DBA](../dev/index.md) yourself if you don't have one on your team.
 
 In parallel with designing the schema, you need to set up your development environment for interaction with {{ ydb-short-name }}. There are a few main aspects to it, explored below.
 

ydb/docs/en/core/dba/toc_i.yaml

@@ -7,9 +7,16 @@ Main resources:
 - [{#T}](getting-started.md)
 - [{#T}](example-app/index.md)
 - [{#T}](yql-tutorial/index.md)
+- Choosing a primary key for:	
+  - [Row-oriented tables](primary-key/row-oriented.md)	
+  - [Column-oriented tables](primary-key/column-oriented.md)	
+- [{#T}](secondary-indexes.md)
 - [{#T}](batch-upload.md)
 - [{#T}](paging.md)
 - [{#T}](timeouts.md)
+- [{#T}](system-views.md)
+- [{#T}](cdc.md)
+- [{#T}](custom-attributes.md)	
 - Reference:
   - [{#T}](../yql/reference/index.md)
   - [{#T}](../reference/ydb-sdk/index.md)

ydb/docs/en/core/dba/toc_p.yaml

@@ -11,9 +11,27 @@ items:
   include:
     mode: link
     path: example-app/toc_p.yaml
+- name: Primary keys
+  include:
+    mode: link
+    path: primary-key/toc_p.yaml
+- name: Secondary indexes
+  href: secondary-indexes.md
+- name: Query plans optimization
+  href: query-plans-optimization.md
+  hidden: true
 - name: Batch upload
   href: batch-upload.md
 - name: Paging
   href: paging.md
 - name: Timeouts
-  href: timeouts.md
+  href: timeouts.md
+- name: System views
+  href: system-views.md
+- name: Change Data Capture
+  href: cdc.md
+- name: Terraform
+  href: terraform.md
+  hidden: true
+- name: Custom attributes
+  href: custom-attributes.md

ydb/docs/en/core/dba/cdc.md renamed to ydb/docs/en/core/dev/cdc.md

@@ -13,15 +13,15 @@ Backups protect against data loss by letting you restore data.
 
 ### Files {#files}
 
-To back up data to a file, run the `ydb tools dump` command. To learn more about this command, follow the [link](../reference/ydb-cli/export-import/tools-dump.md) to the {{ ydb-short-name }} CLI reference.
+To back up data to a file, run the `ydb tools dump` command. To learn more about this command, follow the [link](../../reference/ydb-cli/export-import/tools-dump.md) to the {{ ydb-short-name }} CLI reference.
 
-To restore data from a backup, run the `ydb tools restore` command. To learn more about this command, follow the [link](../reference/ydb-cli/export-import/tools-restore.md) to the {{ ydb-short-name }} CLI reference.
+To restore data from a backup, run the `ydb tools restore` command. To learn more about this command, follow the [link](../../reference/ydb-cli/export-import/tools-restore.md) to the {{ ydb-short-name }} CLI reference.
 
 ### S3-compatible storage {#s3}
 
-To back up data to S3-compatible storage (such as [AWS S3](https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html)), run the `ydb export s3` command. To learn more about this command, follow the [link](../reference/ydb-cli/export-import/export-s3.md) to the {{ ydb-short-name }} CLI reference.
+To back up data to S3-compatible storage (such as [AWS S3](https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html)), run the `ydb export s3` command. To learn more about this command, follow the [link](../../reference/ydb-cli/export-import/export-s3.md) to the {{ ydb-short-name }} CLI reference.
 
-To restore data from a backup created in S3-compatible storage, run the `ydb import s3` command. To learn more about this command, follow the [link](../reference/ydb-cli/export-import/import-s3.md) to the {{ ydb-short-name }} CLI reference.
+To restore data from a backup created in S3-compatible storage, run the `ydb import s3` command. To learn more about this command, follow the [link](../../reference/ydb-cli/export-import/import-s3.md) to the {{ ydb-short-name }} CLI reference.
 
 {% include [_includes/backup_and_recovery/cli_overlay.md](_includes/backup_and_recovery/cli_overlay.md) %}
 

ydb/docs/en/core/dba/custom-attributes.md renamed to ydb/docs/en/core/dev/custom-attributes.md

@@ -7,6 +7,7 @@ Main resources:
 - [{#T}](../../deploy/index.md)
 - [{#T}](../../maintenance/manual/index.md)
 - [{#T}](../../devops/manual/monitoring.md)
+- [{#T}](logging.md)
+- [{#T}](backup-and-recovery.md)
 - [{#T}](../../reference/embedded-ui/index.md)
 - [{#T}](system-views.md)
-- [{#T}](logging.md)

ydb/docs/en/core/dev/getting-started.md

@@ -8,7 +8,7 @@ Hereinafter, in the descriptions of available fields, the **Key** column contain
 
 {% note info %}
 
-There are also similar system views describing what's happening inside a given database, they are covered in a [separate article for DBAs](../../dba/system-views.md).
+There are also similar system views describing what's happening inside a given database, they are covered in a [separate article for DBAs](../../dev/system-views.md).
 
 {% endnote %}
 

ydb/docs/en/core/dev/index.md

@@ -9,8 +9,12 @@ items:
   include:
     mode: link
     path: ../../maintenance/manual/toc_p.yaml
+- name: Backup and recovery
+  href: backup-and-recovery.md
 - name: Monitoring
   href: monitoring.md
+- name: Logging
+  href: logging.md
 - name: Updating YDB
   href: upgrade.md
 - name: Changing an actor system's configuration
@@ -19,5 +23,4 @@ items:
   href: ../../maintenance/manual/cms.md
 - name: System views
   href: system-views.md
-- name: Logging
-  href: logging.md
+

ydb/docs/en/core/dba/primary-key/column-oriented.md renamed to ydb/docs/en/core/dev/primary-key/column-oriented.md

@@ -29,7 +29,7 @@ To design a primary key properly, follow the rules below.
 * The fewer table partitions a query uses, the faster it runs. For greater performance, follow the one query — one partition rule.
 * Avoid situations where a small part of the DB is under much heavier load than the rest of the DB.
 
-For more information, see [choosing a primary key](../../dba/primary-key/index.md).
+For more information, see [choosing a primary key](../../dev/primary-key/index.md).
 
 #### How do I evenly distribute load across table partitions? {#balance-shard-load}
 
@@ -40,7 +40,7 @@ You can use the following techniques to distribute the load evenly across table
    * use a hash of the key column values as the primary key.
 * Reduce the number of partitions used in a single query.
 
-For more information, see [choosing a primary key](../../dba/primary-key/index.md).
+For more information, see [choosing a primary key](../../dev/primary-key/index.md).
 
 #### Can I use NULL in a key column? {#null}
 

ydb/docs/en/core/dba/primary-key/index.md renamed to ydb/docs/en/core/dev/primary-key/index.md

@@ -16,12 +16,12 @@ links:
   - title: For DevOps
     description: How to run production YDB clusters
     href: devops/
-  - title: For DBA
-    description: How to run manage YDB databases
-    href: dba/
   - title: For Developers
     description: How to develop applications working with YDB
     href: dev/
+  - title: For Security Engineers
+    description: How to secure YDB clusters
+    href: security/
   - title: For Contributors
     description: How to contribute to YDB core and satellite projects
     href: contributor/

ydb/docs/en/core/dba/primary-key/row-oriented.md renamed to ydb/docs/en/core/dev/primary-key/row-oriented.md

@@ -142,7 +142,7 @@ As you can see, it is a simple key-value table. Let's walk through the query ste
 * Each SQL statement kind like `CREATE TABLE` has more detailed explanation in [YQL reference](yql/reference/index.md).
 * `example` is the table name identifier, while `key` and `value` are column name identifiers. It is recommended to use simple names for identifiers like these, but if you need one that contains non-trivial symbols, wrap the name in backticks.
 * `UInt64` and `String` are data type names. `String` represents a binary string, and `UInt64` is a 64-bit unsigned integer. Thus, our example table stores string values identified by unsigned integer keys. More details [about data types](yql/reference/types/index.md).
-* `PRIMARY KEY` is one of the fundamental concepts of SQL that has a significant impact on both application logic and performance. Following the SQL standard, the primary key also implies an unique constraint, meaning the table cannot have multiple rows with equal primary keys. In this example table, it's quite straightforward which column should be chosen as the primary key, which we specify as `(key)` in round brackets after the respective keyword. In real-world scenarios, tables often have dozens of columns, and primary keys can be compound (consisting of multiple columns in a specified order), making choosing the right primary key more of an art. If you are interested in this topic, there's a [guide on choosing the primary key for maximizing performance](dba/primary-key/row-oriented.md). YDB tables are required to have a primary key.
+* `PRIMARY KEY` is one of the fundamental concepts of SQL that has a significant impact on both application logic and performance. Following the SQL standard, the primary key also implies an unique constraint, meaning the table cannot have multiple rows with equal primary keys. In this example table, it's quite straightforward which column should be chosen as the primary key, which we specify as `(key)` in round brackets after the respective keyword. In real-world scenarios, tables often have dozens of columns, and primary keys can be compound (consisting of multiple columns in a specified order), making choosing the right primary key more of an art. If you are interested in this topic, there's a [guide on choosing the primary key for maximizing performance](dev/primary-key/row-oriented.md). YDB tables are required to have a primary key.
 
 ## Add sample data
 

ydb/docs/en/core/dba/primary-key/toc_p.yaml renamed to ydb/docs/en/core/dev/primary-key/toc_p.yaml

@@ -10,7 +10,7 @@ By using the `table index` command, you can create and delete [secondary indexes
 
 You can also add or delete a secondary index with the [ADD INDEX and DROP INDEX](../../../../yql/reference/syntax/alter_table.md#secondary-index) directives of YQL ALTER TABLE.
 
-To learn about secondary indexes and their use in application development, see [Secondary indexes](../../../../dba/secondary-indexes.md) under "Recommendations".
+To learn about secondary indexes and their use in application development, see [Secondary indexes](../../../../dev/secondary-indexes.md) under "Recommendations".
 
 ## Creating a secondary index {#add}
 

ydb/docs/en/core/dba/query-plans-optimization.md renamed to ydb/docs/en/core/dev/query-plans-optimization.md

@@ -11,10 +11,6 @@ items:
   include:
     mode: link
     path: devops/toc_p.yaml
-- name: For DBA
-  include:
-    mode: link
-    path: dba/toc_p.yaml
 - name: For Developers
   include:
     mode: link