Kubernetes vs. Watson IoT Platform

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

For large companies with large-scale manufacturing, electronics management, and infrastructures that require lots of maintenance, IBM Watson IoT is a must-have. It greatly increases performance, decreases downtime, and is an all-around great management dashboard. This is best for infrastructures that have a larger infrastructures of IoT devices in an enterprise/manufacturing setting, otherwise IBM Watson may not bring many benefits to your team.

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• The asset information is available in both static and dynamic format (from thermal images, to OEM data, to time series data). The ability to ingest all the information using a single platform has great value.
• Another benefit is a seamless integration with Maximo. This has been a challenge with other 3rd party systems available.
• The experience of IBM Maximo systems updates is positive.

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

• Some of the tutorials could use a little more improvement - While there is a considerable amount of documentation, most of the good documentation for Watson IoT we found to be from third-parties.
• Administration and billing tools could use a bit more improvement - The UI is a bit clunky and poorly-designed here.
• Be prepared to work with IBM support to get this going - Their turn-around support for inquiries can be lengthy, and setup time may also be quite lengthy because of this.

Incentivized

The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.

It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

Predix has recently launched their Asset Performance management Unified system. I am keen to see how it stacks up against Watson.

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized

• Positive - This tool greatly increases most company's manufacturing and production efficiency, and the use-cases are extensive. It was a great way of decreasing down-time for us.
• Negative - Took lots of work and energy to get up and running, we had to rely on IBM support and tutorials many times during this process.
• Positive - Quite cheap, most of the tiers of pricing cost very little, and it's possible to use Watson IoT for a few months for free to see if it is beneficial for your company.

Incentivized