Amazon Web Services (AWS) Provides the Amazon Simple Queue Service (SQS), a managed message queue service which supports the safe decoupling and distribution of different components in a cloud infrastructure and cloud applications.
$0
per GB
AWS IoT Core
Score 9.9 out of 10
N/A
AWS IoT Core is a managed cloud service that lets connected devices interact with cloud applications and other devices. It includes the Device Gateway and the Message Broker, which connect and process messages between IoT devices and the cloud. AWS IoT Core connects AWS and Amazon services like AWS Lambda, Amazon Kinesis, Amazon S3, Amazon SageMaker, Amazon DynamoDB, Amazon CloudWatch, AWS CloudTrail, Amazon QuickSight, and Alexa Voice Service to build IoT applications that gather, process,…
$0.08
Per Million Minutes
Pricing
Amazon Simple Queue Service (SQS)
AWS IoT Core
Editions & Modules
All Data Transfer In
$0.00
per GB
Standard Queue
$0.00000004
per request
FIFO Queue
$0.00000005
per request
Connectivity
$0.08
Per Million Minutes
Rules Engine
$0.15
Per Million Actions
Messaging
$1.00
Per Million Messages
Offerings
Pricing Offerings
Amazon SQS
AWS IoT Core
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Simple Queue Service (SQS)
AWS IoT Core
Considered Both Products
Amazon SQS
Verified User
Anonymous
Chose Amazon SQS
Simple and quick implementation makes it a first go to service when not familiar with queue management. Handling of Dead messages in queue is helpful, as over time these messages stack up causing lots of unnecessary processing at listener end. Retry mechanism for failed …
I wanted to select "RabbitMQ" instead of IBM Cloud Messages for RabbitMQ.... At first, we have some instances running RabbitMQ but SQS is a fully managed queuing service it was way more convenient to use it and get rid of RabbitMQ !
To be blunt: Amazon SQS was the simplest to implement given our requirements. Other services in this space work just as well, and SQS does not have any benefits outside of being the easiest to implement when using an otherwise fully AWS stack. AWS itself even has other …
The reason for the choice is due to maintenance needs and HIPPA compliance, as well as the great options under the AWS ecosystem, with very useful configurable parameters.
The most comparable products are RabbitMQ, and perhaps ActiveMQ. Until recently, AWS did not offer a managed ActiveMQ product. Running RabbitMQ will never be to my team's competitive advantage; we wanted a managed service.
Amazon SQS stacks up with the best of them as most of their products do. The only issue comparatively that I’ve had with this service, in particular, is the silently failing messages and then allocation of time to dedicate to debugging when the issue of why a message got stuck …
Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this …
AWS iot core is a good starting point which can be utilized for a variety of enterprise solutions. Barrier to entry to experiment and try AWS iot core is less and AWS eco-system providers ensure that even startups can try a variety of solutions and build key skills and …
Azure IoT service provides more or less the same services as compared to AWS IoT core, however the costing of AWS lead us to continued usage of IoT core over Azure IoT services. Also, considering our existing technology stack is on AWS, it was a natural selection for better …
It turns out that AWS IoT Core is the most mature solution on the market with the best variety of integration tools available. On the downside, it is not the cheapest platform existing out there. Amazon IoT Core is easy to start and set up, and our prior engagement with Amazon …
For our use case, we ended up with AWS because the human resources that were planning to be resourced on this particular project happened to have prior familiarity with the AWS ecosystem. The conversation became can we justify continuing with this ecosystem rather than pivoting …
We have checked other IoT platforms such as IBM Watson IoT and Microsoft Azure IoT, but Amazon IoT Core seems reasonable in terms of pricing and overall functionalities. Amazon IoT Core is easy to start and set up and our prior engagement with Amazon for AWS was a factor to go …
AWS IoT Core is faster, easier, cheaper, and enjoyed by our employees more than Microsoft Azure. We selected AWS IoT because we saw an advertisement for it and have used it ever since. We will continue to use it as long as it is around or until we find one that is better.
We prefer Amazon storage and content delivery S3 services rather than Microsoft Blob Storage. Also, AWS IoT Core seems to be the cheaper alternative compared to Azure IoT.
While we use AmazonSimple Queue Service (SQS) in our serverless applications, it would be a great option to handle queue management for any internet-connect application. It provides the most benefit in situations where your application or service must maintain mission-critical queue of messages or jobs. If you're already using other AWS services you will find the greatest benefit.
AWS iot core is very useful if you need to scale very quickly for managing lots of devices without handling the underlying infrastructure cost. It can enable real time publishing and subscription of devices, monitoring and early stage intervention in case of unexpected issues while developing a full stack solution. However, healthcare scenarios where government intervention is needed should be developed and scaled by following the set of compliance policies of the government and the SLA requirements of the customer. Finally, it is great where you need to do data science research after anonymizing data
I give AWS IoT Core's overall usability this rating because it is very easy to use and is enjoyed by all of our staff. The only problem is that it sometimes glitches and it freezes a lot. So overall, the usability of AWS IoT Core is very good, and we will continue to use it.
Online blogging and documentation for SQS is great. There are many examples of implementing it and if you look hard enough, more than likely there are examples that meet the exact case with which you are working
It covers all the aspects of IoT services required for an IoT company. It supports all the industry-wide protocols for secure data transmission and integrates powerful AL and ML technology for data analytics. For data storage, Amazon S3 is a great solution. Strong tech support and user community. Since it is widely used as compared to other products, there is an abundance of training and learning material on the web.
To be blunt: Amazon SQS was the simplest to implement given our requirements. Other services in this space work just as well, and SQS does not have any benefits outside of being the easiest to implement when using an otherwise fully AWS stack. AWS itself even has other solutions that would work just as well, however, SQS had the most reasonable pricing model for our given situation. That will certainly not always be the case, but in several of the instances where we are using it, it just made the most sense.
Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this point.