Skip to content

Commit 604c9c4

Browse files
docs(srv): add triangle links to serverless MTA-6405 (#5438)
* docs(srv): add triangle links to serverless MTA-6405 * docs(srv): update * docs(srv): update * docs(srv): update
1 parent de965d3 commit 604c9c4

File tree

4 files changed

+37
-45
lines changed

4 files changed

+37
-45
lines changed
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
macro: serverless-Concepts
3+
---
4+
## Serverless Containers
5+
6+
Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
7+
8+
It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
9+
10+
Refer to the [Serverless Containers Quickstart](/serverless-containers/quickstart/) for more information on how to deploy and use a container.
11+
12+
## Serverless Functions
13+
14+
Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
15+
16+
These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
17+
18+
Refer to the [Serverless Functions Quickstart](/serverless-functions/quickstart/) for more information on how to deploy and invoke a function.
19+
20+
## Serverless Jobs
21+
22+
Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-containers/reference-content/difference-jobs-functions-containers) for more information.
23+
24+
Refer to the [Serverless Jobs Quickstart](/serverless-jobs/quickstart/) for more information on how to create and execute a job.

pages/serverless-containers/concepts.mdx

Lines changed: 7 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ tags: containers cold-start concurrency container-registry environment-variables
55
dates:
66
validation: 2025-05-26
77
---
8+
import ServerlessConcepts from '@macros/serverless/serverless-concepts.mdx'
9+
810

911
## Arguments
1012

@@ -165,6 +167,8 @@ A NATS trigger is a mechanism that connects a container to a [NATS](/nats/concep
165167
For each message that is sent to a NATS subject, the NATS trigger reads the message and invokes the associated container with the message as the input parameter.
166168
The container can then process the message and perform any required actions, such as updating a database or sending a notification.
167169

170+
Refer to the [dedicated documenation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to add triggers to a Serverless Container.
171+
168172
## Port
169173

170174
The port of a containerized application refers to the network port that the application inside the container listens on for incoming requests.
@@ -198,6 +202,8 @@ A queue trigger is a mechanism that connects a container to a queue created with
198202
For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
199203
The container can then process the message, and perform any required actions, such as updating a database or sending a notification.
200204

205+
Refer to the [dedicated documenation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to add triggers to a Serverless Container.
206+
201207
## Registry endpoint
202208

203209
The registry endpoint parameter is the resource linked to the container image used in your Serverless Container.
@@ -246,21 +252,7 @@ For more details about the advantages of using Serverless, [read the Serverless
246252

247253
Serverless.com (Serverless Framework) is a tool that allows you to deploy serverless applications without having to manage Serverless Container's API call. Write and deploy a YAML configuration file, everything else is handled automatically, even the image building.
248254

249-
## Serverless Containers
250-
251-
Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
252-
253-
It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
254-
255-
## Serverless Functions
256-
257-
Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
258-
259-
These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
260-
261-
## Serverless Jobs
262-
263-
Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-containers/reference-content/difference-jobs-functions-containers) for more information.
255+
<ServerlessConcepts />
264256

265257
## Stateless
266258

pages/serverless-functions/concepts.mdx

Lines changed: 4 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ dates:
66
validation: 2025-05-27
77
---
88

9+
import ServerlessConcepts from '@macros/serverless/serverless-concepts.mdx'
10+
11+
912
## Autoscaling
1013

1114
Autoscaling refers to the ability of Serverless Functions to automatically adjust the number of instances without manual intervention.
@@ -181,21 +184,7 @@ For more details about the advantages of using Serverless, [read the Serverless
181184

182185
Serverless.com (Serverless Framework) is a tool that enables the deployment of serverless applications without having to manage Serverless Function's API call. Just write your configuration in a YAML and deploy, it handles everything.
183186

184-
## Serverless Containers
185-
186-
Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
187-
188-
It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
189-
190-
## Serverless Functions
191-
192-
Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
193-
194-
These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
195-
196-
## Serverless Jobs
197-
198-
Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-functions/reference-content/difference-jobs-functions-containers) for more information.
187+
<ServerlessConcepts />
199188

200189
## Stateless
201190

pages/serverless-jobs/concepts.mdx

Lines changed: 2 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ dates:
66
validation: 2025-06-09
77
posted: 2023-11-07
88
---
9+
import ServerlessConcepts from '@macros/serverless/serverless-concepts.mdx'
910

1011
## Container Registry
1112

@@ -59,21 +60,7 @@ Refer to the [dedicated FAQ](/serverless-jobs/faq/#how-can-i-configure-access-to
5960

6061
A schedule (cron) is a mechanism used to automatically start a Serverless Job at a specific time on a recurring schedule. It works similarly to a traditional Linux cron job, using the `* * * * *` format. Refer to our [cron schedules reference](/serverless-jobs/reference-content/cron-schedules/) for more information.
6162

62-
## Serverless Containers
63-
64-
Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
65-
66-
It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
67-
68-
## Serverless Functions
69-
70-
Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
71-
72-
These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
73-
74-
## Serverless Jobs
75-
76-
Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparison between Serverless products](/serverless-jobs/reference-content/difference-jobs-functions-containers) for more information.
63+
<ServerlessConcepts />
7764

7865
For more details about advantages of using Serverless, [read the Serverless overview page](/serverless-jobs/reference-content/serverless-overview/).
7966

0 commit comments

Comments
 (0)