Skip to content

add managed database calculation methodology#6178

Open
eauvray-github wants to merge 5 commits intomainfrom
int-add-efp_rdb_methodo
Open

add managed database calculation methodology#6178
eauvray-github wants to merge 5 commits intomainfrom
int-add-efp_rdb_methodo

Conversation

@eauvray-github
Copy link
Contributor

Your checklist for this pull request

Description

Add information about managed database environmental footprint calculation methodology

@eauvray-github eauvray-github requested review from a team as code owners February 10, 2026 14:59
@eauvray-github
Copy link
Contributor Author

eauvray-github commented Feb 10, 2026

please do not merged now, it's not in production yet

Co-authored-by: Néda <87707325+nerda-codes@users.noreply.github.com>
- **Backups & snapshots**: Automated or manual backups are stored using Object Storage. We apply the [Object Storage environmental footprint methodology](/environmental-footprint/additional-content/object-storage-env-footprint/) based on the size of the stored backups. If you create snapshots of your database volume, we apply the [Block Storage snapshot methodology](/environmental-footprint/additional-content/block-storage-env-footprint/).

- **Control plane**: The control plane represents the shared infrastructure managed by Scaleway to orchestrate, monitor, and maintain your databases. We allocate a fixed share of the global control plane's power consumption and manufacturing impact to each active database node.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

### MongoDB

For MongoDB, the carbon footprint is the sum of the impact of:
- **The nodes**: Your MongoDB® nodes are effectively Kubernetes nodes running on specific Instance types. We apply the Kubernetes [Kapsule environmental footprint methodology](/environmental-footprint/additional-content/kubernetes-env-footprint/). As your cluster scales (adding nodes for performance or redundancy), the footprint increases linearly with the number of underlying instances reserved.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **The nodes**: Your MongoDB® nodes are effectively Kubernetes nodes running on specific Instance types. We apply the Kubernetes [Kapsule environmental footprint methodology](/environmental-footprint/additional-content/kubernetes-env-footprint/). As your cluster scales (adding nodes for performance or redundancy), the footprint increases linearly with the number of underlying instances reserved.
- **Nodes**: Your MongoDB® nodes are effectively Kubernetes nodes running on specific Instance types. We apply the Kubernetes [Kapsule environmental footprint methodology](/environmental-footprint/additional-content/kubernetes-env-footprint/). As your cluster scales (adding nodes for performance or redundancy), the footprint increases linearly with the number of underlying instances reserved.

- **Snapshots**: If you create snapshots of your database volume, we apply the [Block Storage snapshot methodology](/environmental-footprint/additional-content/block-storage-env-footprint/).

- **Control plane**: The control plane represents the shared infrastructure managed by Scaleway to orchestrate, monitor, and maintain your databases. We allocate a fixed share of the global control plane's power consumption and manufacturing impact to each active database node.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com>
@SamyOubouaziz SamyOubouaziz added the do not merge PR that shouldn't be merged before a specific date (eg release) label Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge PR that shouldn't be merged before a specific date (eg release)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants