Overall Satisfaction with IBM Cloud Kubernetes Service
We provide multiple blockchain api service solution to our client for a proxy voting application used by major stock transfer company in usa. Our blockchain api were hosted and manages inside the IBM [Cloud Kubernetes Service]. The [IBM Cloud Kubernetes Service] has been used by all across the department among the company.
- Service dashboard can be loaded with more goto information
- Disk, persistent volume etc should be also easy to access from service dashboard
- Updating node and kubernetes version is pretty hassle some
- [IBM Cloud Kubernetes Service] is bit Costly
We hardly use internal dashboard rather we used infrastructure as code from our development side.
We haven't use that service in any of our products.
- Amazon Managed Streaming for Apache Kafka (Amazon MSK), MySQL, Hyperledger Fabric, Amazon S3 (Simple Storage Service), IBM Cloud Virtual Private Cloud (VPC), Ubuntu Linux and IBM Cloud Certificate Manager
We mainly selected [IBM Cloud Kubernetes Service] because IBM fabric blockchain service is mostly compatible with it. To have all the infrastructure in a single cloud to get the best output we selected the [IBM Cloud Kubernetes Service].
- IBM Cloud Foundry
- IBM Cloud Virtual Servers
- IBM Cloud Container Registry
- IBM Cloud Object Storage
- IBM Cloud Databases
- IB M Blockchain Platform
- IBM Event Streams (formerly MessageHub)
Best impact we get were all the components are deployed into same zone cloud so connectivity wise it's fast and reliable. Using multiple ibm service make it more easy to manage all the infrastructure in a single place as we are mainly a private blockchain service provider. Our goal is to provide best private blockchain experience to our customers.
- in-person training
- no training