Easily connect services and enable asynchronous communication between microservices. Send messages and events without having to manage a message broker.
Scaleway’s Messaging & Queuing supports various protocols (SNS, SQS, NATS) and is built on open-source components (NATS, Benthos). We support your multi-cloud strategy and make it easy for you to port your applications. Easily transition from other systems.
Fully managed message broker solution to help you easily create microservices-based applications, send asynchronous messages and events, and simplify application development, especially with Serverless.
Achieve higher fault tolerance and resilience by enabling asynchronous service-to-service communication between microservices. Should a system’s service become unreachable, the other services can still continue to interact with the queue.
Enable async messaging for inter-service communication between microservices, decoupling them and buffering requests to allow independent tasks, making debugging, testing, and scaling easier.
Queue your data to ensure that it will remain persistent and be processed smoothly even during traffic spikes.
Send messages to several consumers, fan out (subscribe multiple queues to the same topic to replicate a message over multiple queues), and use Message Filtering to receive only a subset of the messages.
Increase your application performance by using parallel compute workers that will process messages or event stores in queues.
Based on open standards. Enable a multi-cloud approach to ease your microservice porting. Use AWS SQS, AWS SNS,or NATS API to send and receive messages or configure the queue.
Distribute notifications and events across several consumers using a publish/subscribe pattern.
FIFO queues with deduplication enabling exactly-once messaging. We provide enhanced queue features such as Dead Letter Queue and Long Polling, and enable replay for messages stored in Stream using NATS JetStream.
With the Scaleway Serverless integration, you can trigger Functions or Containers with events stored in SQS queues and NATS Stream.
With Restricted Access and encryption in transit, we ensure secure asynchronous communication between microservices.
An easy-to-use, fully managed infrastructure, a message broker solution that’s integrated into Scaleway’s console and tools (CLI, SDK, Terraform) to simplify application development, especially with Serverless.
Based in France with builders and customers all over the world, our services are located within the European Union and protected by its regulations.
100% of electricity consumed in our data centers comes from renewable energy. Decommissioned hardware are securely reused & recycled.
Our technical assistance is available 24/7 to answer all your questions and assist you. Upgrade your support plan to reach our assistance team directly by phone.
Our services are designed to offer you the best price/performance ratio, with straightforward billing to grow your business and keep your expenses under control.
Scaleway’s Messaging & Queuing product is a message broker tool that allows you to transfer messages between different microservices and platforms. This enables them to “talk” to each other effectively even if they are otherwise incompatible. Messaging & Queuing enables and simplifies the development of microservices applications, and allows you to build highly scalable, reliable, distributed applications.
A namespace sets a scope for your queues, topics, and credentials. For each namespace, you can generate one or multiple sets of credentials to perform actions within that namespace. Read more about namespaces.
NATS, SNS, and SQS are all messaging protocols supported by Scaleway’s Messaging & Queuing offer. You can find out more about these protocols, and other essential Messaging & Queuing concepts, on our dedicated concepts page.
It is currently not possible for an SQS queue to subscribe to a topic located in a different namespace.
We currently implement the API endpoints listed here, which makes Scaleway’s Messaging & 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 the region and the URL to ensure compatibility.
The following subscriber types are supported:
We cannot currently disclose the future pricing of the product. However, regardless of which messaging protocol you choose, you will be billed based on the message volume (sent/received) transiting through the system each month.
