You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 20, 2025. It is now read-only.
Each cloud provider comes with a set of default services used when deploying resources. You can find the default services for each cloud provider below.
Copy file name to clipboardExpand all lines: docs/batch.mdx
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -239,3 +239,13 @@ void main() {
239
239
```
240
240
241
241
</CodeSwitcher>
242
+
243
+
## Cloud Service Mapping
244
+
245
+
Each cloud provider comes with a set of default services used when deploying resources. You can find the default services for each cloud provider below.
246
+
247
+
-[AWS](/providers/mappings/aws/batch)
248
+
- Azure - Coming soon
249
+
-[Google Cloud](/providers/mappings/gcp/batch)
250
+
251
+
If you need support for additional clouds, let us know by [opening an issue](https://github.com/nitrictech/nitric/issues) or joining the conversation on [Discord](https://nitric.io/chat).
Copy file name to clipboardExpand all lines: docs/keyvalue.mdx
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -437,3 +437,11 @@ keys.forEach((String key) {
437
437
```
438
438
439
439
</CodeSwitcher>
440
+
441
+
## Cloud Service Mapping
442
+
443
+
Each cloud provider comes with a set of default services used when deploying resources. You can find the default services for each cloud provider below.
It's common to ask when to use a queue or a topic. From a publisher's point of view, both queues and topics are almost identical. The difference is primarily on the receiver/subscriber side. Topics push new messages to their subscribers, immediately spinning up workers to process them, while queues rely on the receiver to ask for new messages to process.
703
703
704
704
For these reasons, we usually default to Topics. Queues are more suitable for batch workloads or situations where there are occasional surges of requests that can be processed at a later time.
705
+
706
+
## Cloud Service Mapping
707
+
708
+
Each cloud provider comes with a set of default services used when deploying resources. You can find the default services for each cloud provider below.
Copy file name to clipboardExpand all lines: docs/providers/custom/extend.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ You'll notice that we also override the `Bucket` value to use the pulumi spaces
135
135
136
136
### Config
137
137
138
-
Now we can create an extension configuration to allow adding digital ocean configuration to our stack file. You can find the base AWS configuration [here](../pulumi/aws/configuration).
138
+
Now we can create an extension configuration to allow adding digital ocean configuration to our stack file. You can find the base AWS configuration [here](/providers/pulumi/aws#stack-configuration).
139
139
140
140
Start by defining the type of configuration we want. To deploy to digital ocean we require setting a Digital Ocean token as well as a spaces key, secret, and region.
Copy file name to clipboardExpand all lines: docs/providers/index.mdx
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,18 +34,21 @@ The following is a description of the underlying cloud services that each of the
34
34
35
35
Currently, both the Pulumi and Terraform providers use the same underlying cloud services to deploy your application. The following table shows the cloud services used by default on each cloud:
The code is open-source on [GitHub](https://github.com/nitrictech/nitric), so you can see exactly how resources are deployed and handled at runtime, then make any changes you see fit.
The code is open-source on [GitHub](https://github.com/nitrictech/nitric), so you can see exactly how resources are deployed and handled at runtime, then make any changes you see fit. Some features may be unimplemented, but any interest or requests are appreciated. Let us know on [Discord](https://nitric.io/chat) or by creating an issue on our [GitHub repository](https://github.com/nitrictech/nitric/issues).
0 commit comments