AWS IoT Core vs. Azure Service Bus

End-to-end encryption is an amazing feature because we use IoT to connect to various devices in order to gather data/ stats in real-time. We're able to publish solutions with ease and at a faster rate because of AWS IoT Core. However, its inability to interact with other IoT tools is a big con that I would like them to improve upon.

Incentivized

If you need a cloud-based service bus or a simple to use queue/topic/routing/pub-sub service, then Azure Service Bus is a very good choice at a reasonable price and performance. Typically on-premise we'd use RabbitMQ because it "just works", but if you're building a "cloud-first" application, then this is the one to go with. It's especially easy to integrate with if you're already embedded in the Microsoft ecosystem.

Incentivized

• AWS IoT Core integrates power analytics and an AI solution for sensor data processing.
• Great protocol support including HTTPs and MQTT required to connect resource constraint IoT devices to cloud
• High security standards during data transmission
• Scalability and a great user community

Incentivized

• Acting as a basic queuing service it works very well.
• One of the best parts is that Azure Service Bus can work over HTTPS which helps in strict firewall situations. There is a performance hit if you choose to use HTTPS.
• The routing capabilities are quite good when using topics and subscriptions. You can apply filters using a pseudo-SQL-like language though the correlation filters are quick and easy options.
• Costs are very reasonable at low-ish volumes. If you're processing 10's of millions of messages a month... it may be a different story.

Incentivized

• Ability to integrate with Ethercalc software solution
• Ability to introduce NFC toolchains and systems which could be utilized in iot modular gateway solutions like drones
• Ability to reduce latency as the solution scales is very much needed
• Hybrid solution which can integrate other existing iot solutions into AWS iot core

Incentivized

• The SqlFilter could be a little easier to use, but it's not terrible.
• The performance while using HTTPS for the connection is a little slow compared to direct connections using AMQP ports.
• There is a size limit to the message - unlike RMQ for instance, Azure Service Bus caps messages to 256kb on the standard tier.

Incentivized

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.

Incentivized

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.

Incentivized

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 integration and ease of use.

Incentivized

RabbitMQ is simple and awesome... but so is Azure Service Bus. Both accomplish the same thing but in different environments. If you're building a cloud-native application - especially one that is serverless by design - Azure Service Bus is the only real choice in Azure. It works well, it's performance, and it's reasonably priced in the Standard tier. From our testing, RMQ is more performant, but it's hard to compare service-based implementations vs RMQ installed on VMs.

Incentivized

• Gives confidence to prototype iot solutions across lots of devices in little time
• Ability to meet requirements for managing a variety of communication protocols
• Learning iot analytics and visualization for faster insights enablement
• Onboarding devices and managing quickly without building inhouse solutions

Incentivized

• Compared to open-source free software like RMQ, Azure Service Bus does have some costs to it. But the cost is reasonable.
• Also unlike RMQ, Azure Service Bus doesn't require you to stand up any hardware - so it's very easy to use and saves time/money from that perspective.

Incentivized