Amazon Kinesis vs. Microsoft Azure IoT Hub

Amazon Kinesis is a great replacement for Kafka and it works better whenever the components of the solution are AWS based. Best if extended fan-out is not required, but still price-performance ratio is very good for simplifying maintenance.

I would go with a different option if the systems to be connected are legacy, for instance in the case of traditional messaging clients.

Incentivized

We are using the Azure IOT hub for solving the multitenancy problem within our research project. We are consuming data from various resources and communicating it with different devices on our hybrid cloud. We also use Azure IoT as a bridge between two business Intelligence sources which are really hard to connect devices.

Incentivized

• Processing huge loads of data
• Integrating well with IoT Platform on Amazon
• Integration with overall AWS Ecosystem
• Scalability

Incentivized

• Massive registration and deployment of new devices.
• Easy integration with other Azure services.
• Handling security if devices.

Incentivized

• Not a queue system, so little visibility into "backlog" if there is any
• Confusing terminology to make sure events aren't missed
• Sometimes didn't seem to trigger Lambda functions, or dropped events when a lot came in

Incentivized

• Hardware and embedded integration could improve or be at parity with competitor.
• Pricing model not as flexible as competitor.

Incentivized

The documentation was confusing and lacked examples. The streams suddenly stopped working with no explanation and there was no information in the logs. All these were more difficult when dealing with enhanced fan-out. In fact, we were about to abort the usage of Kinesis due to a misunderstanding with enhanced fan-out.

Incentivized

Azure IoT support professionals are strong, and always provide timely responses. Vast documentation and examples are available, plus a network of professionals in the market. It's very comparable to the main competitor offer, and easily integrated into the main Azure product offer. Azure IoT is not a new solution, so it is very mature and support can easily address any day to day or architectural concern you have.

Incentivized

The main benefit was around set up - incredibly easy to just start using Kinesis. Kinesis is a real-time data processing platform, while Kafka is more of a message queue system. If you only need a message queue from a limited source, Kafka may do the job. More complex use cases, with low latency, higher volume of data, real time decisions and integration with multiple sources and destination at a decent price, Kinesis is better.

Incentivized

We require Azure integration, data security and simple development. IoT Hub ticked all those boxes.

Incentivized

• Caused us to need to re-engineer some basic re-try logic
• Caused us to drop some content without knowing it
• Made monitoring much more difficult
• We eventually switched back to SQS because Kinesis is not the same as a Queue system

Incentivized

• As a student, we are using student program subscription which is cheaper than an individual or business subscription.
• Our school devices our efficiently communicating with each other which has increased the revenue of our school.
• It provides strong and robust cloud communication within the premises which also helped in increased in the school reputation.

Incentivized