AWS IoT Core vs. IBM Cloud Pak for Applications

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

Well suited for customers who are looking for cloud-adoption, and finally to meet the challenges of business innovation for the competitive advantage through DevOps.

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

• Provides a fantastic range of Application runtimes allowing the most suitable runtime to be selected for the app being implemented.
• After using Transformation Advisor for quite a while, it is an indispensable tool to help modernize, specifically from WebSphere and Tomcat, towards the lightweight, fast and efficient Liberty runtime.
• The simplicity of the licensing by wrapping many products into a single offering with a different VPC weighting.
• Allows us to modernize our runtime from WebSphere Application Server (or ND) to WebSphere Liberty core without sacrificing our WAS licenses.

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

• User Experience and Learning Curve
• Integration with Third-party Tools
• Pricing and Licensing Model

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

Our customer mission-critical core banking applications like Temenos T24 run on best of the breed IBM WebSphere Application Server which is java based-application server. IBM has kept up the promise of providing support, fixpack, and any update. As far as I know, at least by 2030, IBM is committed to continue with WHE which gives customers confidence in their current investments.

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

• We have been able to migrate apps away from the expensive WAS-ND to the more cost-effective WAS-base without throwing away our WAS-ND licenses. With a 1:4 ratio of WAS-ND to WAS-base we've been able to we've been able to save in excess of 75% on licensing charges for these apps.
• By having a license model based on VPC ratios (1:4:8 - WAS-ND:WAS-base:Liberty core) we've been able to move away from using license pooling resulting in over-allocating (i.e. wasting) CPU cores for each license pool, to using consolidated license pools hosting a combination of WAS-ND, WAS-base and Liberty-core. This has allowed us to reduce our licensing costs accordingly.

Incentivized