AWS IoT Core vs. Google Cloud Pub/Sub

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 want to stream high volumes of data, be it for ETL streaming or event sourcing, Google Cloud Pub/Sub is your go-to tool. It's easy to learn, easy to observe its metrics and scales with ease without additional configuration so if you have more producers of consumers, all you need to do is to deploy on k8s your solutions so that you can perform autoscaling on your pods to adjust to the data volume. The DLQ is also very transparent and easy to configure. Your code will have no logic whatsoever regarding orchestrating pubsub, you just plug and play. However, if you are not in the Google Cloud Pub/Sub environment, you might have trouble or be most likely unable to use it since I think it's a product of Google Cloud.

• 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

• With a pub/sub architecture the consumer is decoupled in time from the publisher i.e. if the consumer goes down, it can replay any events that occurred during its downtime.
• It also allows consumer to throttle and batch incoming data providing much needed flexibility while working with multiple types of data sources
• A simple and easy to use UI on cloud console for setup and debugging
• It enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalability

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

• Would be nice if the queue could be extended beyond 7 days.
• We found it a bit tricky replay unacknowledged messages when needed.

Incentivized

It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.

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 has many libraries in many languages, google provides either good guides or they're AI generated code libraries that are easy to understand. It has very good observability too.

I have never faced a single problem in 4 years.

It's very fast, can be even better if you use protobuf.

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

They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.

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

Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using GCP only for Pub/Sub the choice depends on other variables.

Incentivized

You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.

• 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

• Increased Efficiency with reliable and Google managed services up all the time wit Disaster Recovery in place as well
• Definitely Lower costs being a cloud based solution and easier to setup
• Faster Project delivery and go to market plan for the business use cases basis this technology at the back end

Incentivized