-
Notifications
You must be signed in to change notification settings - Fork 260
fix(mnq): product split #3873
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
fix(mnq): product split #3873
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
52a4a02
fix(mnq): product split
RoRoJ 4a53764
fix(mnq): split
RoRoJ 9778cdf
fix(mnq): split
RoRoJ f44a9e8
fix(mnq): started screenshots
RoRoJ 9dec906
fix(mnq): finish screenshots
RoRoJ 36d072e
fix(mnq): bugs
RoRoJ 0bf031b
fix(mnq): links
RoRoJ cd718b7
Apply suggestions from code review
RoRoJ 4b1f1ba
fix(mnq): correctionsé
RoRoJ File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,65 +1,46 @@ | ||
| --- | ||
| meta: | ||
| title: Messaging and Queuing FAQ | ||
| description: Discover Scaleway Messaging and Queuing, and get answers to common questions about the different protocols available, compatibility with various services, and billing. | ||
| title: NATS, Queues, and Topics and Events FAQ | ||
| description: Discover Scaleway NATS, Queues, and Topics and Events, and get answers to common questions about the different protocols available, compatibility with various services, and billing. | ||
| content: | ||
| h1: Messaging and Queuing | ||
| dates: | ||
| validation: 2024-09-26 | ||
| validation: 2024-12-04 | ||
| category: serverless | ||
| productIcon: NatsProductIcon | ||
| --- | ||
|
|
||
| ## What is NATS, Queues, and Topics and Events? | ||
|
|
||
| These are three distinct managed message broker tools offered by Scaleway, based on the NATS, SQS and SNS protocols respectively. Previously, these products were grouped together as 'Messaging and Queuing', but have now become three separate products in their own right. | ||
|
|
||
| ## What are NATS, SNS and SQS? | ||
|
|
||
| NATS, SNS and SQS are all messaging protocols supported by Scaleway Messaging and Queuing. You can find out more about these protocols, and other essential Messaging and Queuing concepts, on our dedicated [concepts page](/serverless/messaging/concepts/). | ||
| NATS, SNS and SQS are all messaging protocols used by the Scaleway NATS, Queues, and Topics and Events products. You can find out more about these protocols, and other essential concepts, on our dedicated [concepts page](/serverless/messaging/concepts/). | ||
|
|
||
| ## Is the Scaleway Messaging and Queuing SQS gateway compatible with my application, framework or tool? | ||
| ## Is the Scaleway Queues gateway compatible with my application, framework or tool? | ||
|
|
||
| We currently implement the API endpoints listed [here](/serverless/messaging/reference-content/sqs-support/), which makes Scaleway Messaging and Queuing compatible with the AWS SDK as well as many other tools and frameworks including KEDA and Symfony. Note that you need to specify both Regions and URL to ensure compatibility. | ||
| We currently implement the API endpoints listed [here](/serverless/messaging/reference-content/sqs-support/), which makes Scaleway Queues compatible with the AWS SDK as well as many other tools and frameworks including KEDA and Symfony. Note that you need to specify both Regions and URL to ensure compatibility. | ||
|
|
||
| ## Does Scaleway Messaging and Queuing support all SNS features? | ||
| ## Does Scaleway Topics and Events support all SNS features? | ||
|
|
||
| The following subscriber types are supported: | ||
| - HTTP/S clients | ||
| - Serverless Functions and Containers | ||
| - Scaleway Messaging and Queuing SQS queues | ||
|
|
||
| For more details on supported and unsupported SNS features, see our [dedicated page](/serverless/messaging/reference-content/sns-support/). | ||
|
|
||
| ## Can I configure Messaging and Queuing via Terraform? | ||
|
|
||
| Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider) on configuring Messaging and Queuing with the Terraform [NATS Jetstream provider](https://registry.terraform.io/providers/nats-io/jetstream/latest/docs). | ||
|
|
||
| ## What happened to my Messaging and Queuing namespaces? | ||
|
|
||
| Messaging and Queuing namespaces have been removed. | ||
|
|
||
| **NATS** namespaces and their credentials were automatically migrated to become [NATS accounts](/serverless/messaging/concepts/#nats-account), holding the same credentials you previously had in your namespace(s). You can manage your NATS accounts and namespaces from the new and improved Messaging and Queuing space in the [console](https://console.scaleway.com/) or our [`v1beta1` NATS API](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/). | ||
|
|
||
| **SQS/SNS** namespaces and their credentials were not automatically migrated, and users were warned to **migrate their resources themselves**. | ||
| - Previously these protocols were combined, and shared namespaces/credentials, but now they have been separated. | ||
| - You must [activate](/serverless/messaging/how-to/get-started/#how-to-activate-sqs-or-sns) the SQS and/or SNS protocols on your [Scaleway Project](/identity-and-access-management/organizations-and-projects/concepts/#project). | ||
| - You must [recreate](/serverless/messaging/how-to/create-credentials/) your credentials (and any other resources e.g. queues) for the new "no-namespace" version of Messaging and Queuing. | ||
|
|
||
| The new version of Messaging and Queuing is designed to provide a better and more secure experience, as well as preparing Messaging and Queuing for further integration into the Scaleway ecosystem. | ||
|
|
||
| ## Can I still keep using the old v1alpha1 API? | ||
| - Scaleway Queues queues | ||
|
|
||
| The v1alpha1 API has now been deprecated, and all resources still existing in it deleted. | ||
| For more details on supported and unsupported Topics and Events features, see our [dedicated page](/serverless/messaging/reference-content/sns-support/). | ||
|
|
||
| You must migrate by recreating your SQS and/or SNS resources on the new v1beta1 API (or via the console). NATS resources have been automatically migrated. | ||
| ## Can I configure Scaleway NATS via Terraform? | ||
|
|
||
| - [Messaging and Queuing: SQS v1beta1 API](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/) | ||
| - [Messaging and Queuing: SNS v1beta1 API](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/) | ||
| - [Messaging and Queuing: NATS v1beta1 API](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/) | ||
| Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider) on how to configure Scaleway NATS with the Terraform [NATS Jetstream provider](https://registry.terraform.io/providers/nats-io/jetstream/latest/docs). | ||
|
|
||
| ## How is Messaging and Queuing billed? | ||
| ## How are NATS, Queues, and Topics and Events billed? | ||
|
|
||
| Billing for NATS and SQS is based on: | ||
| Billing is based on: | ||
|
|
||
| - For NATS: [Stream volume](/serverless/messaging/concepts/#stream-volume) (the total sum of each message's size going through the stream) and [stream persistence](/serverless/messaging/concepts/#stream-persistence) (the total amount of data stored * duration) | ||
| - For SQS: [Queue volume](/serverless/messaging/concepts/#queue-volume) (the total sum of each message's size going through the queue) | ||
| - For SNS: [Topic Volume](/serverless/messaging/concepts/#queue-volume)(the total sum of each message's size going out from the topic to the subscriptions) | ||
| - For Queues: [Queue volume](/serverless/messaging/concepts/#queue-volume) (the total sum of each message's size going through the queue) | ||
| - For Topics and Events : [Topic Volume](/serverless/messaging/concepts/#queue-volume)(the total sum of each message's size going out from the topic to the subscriptions) | ||
|
|
||
| For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/). | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.