What Is SharkMQ?
SharkMQ is a managed message queue. Your applications hand messages to SharkMQ, and other applications pick them up when they are ready. If a consumer is slow or offline, messages wait safely instead of being lost.
Two ways to talk to it
| Interface | Use it when | Address |
|---|---|---|
| SQS / SNS-compatible API | Your code already uses Amazon SQS or SNS through an AWS SDK. Change only the endpoint. | https://sqs.cdnshark.com and https://sns.cdnshark.com |
| AMQP 0-9-1 | New code, or any language with an AMQP client library. Push delivery to consumers, exchanges and routing. | amqps://mq.cdnshark.com:5671 |
Both reach the same queues: a message sent through the SQS API can be read over AMQP, and the other way round.
What you get
- Replicated storage. Every queue is copied to three servers in three different buildings. Losing a server, or a whole building, loses no confirmed message.
- Encryption. TLS on every connection, and messages are stored on encrypted disks.
- Your own broker. A private space (a "virtual host") with its own users, queues and limits. Other customers cannot see or reach it.
- Managed in the portal. Users and keys, queues, message counts, peeking at messages and sending test messages are all in SharkMQ in your control panel.
Limits to know
- Messages up to 1 MB (SNS messages up to 256 KB).
- Messages are kept up to 14 days.
- Delivery is at least once: after a failure, a message can arrive twice, so make your consumers safe to repeat.
- A confirmed send waits for a second building to store the message, about 0.15 seconds. Keep several messages in flight (batches, or confirms in the background) for throughput.
Next: Users, Access Keys and Permissions, then Use Your Existing Amazon SQS Code or Connect with AMQP.