Kubernetes vs. Oracle VM

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

Well suited: development work as they provide a very nice free tier, datacenters in Latin America with very low ping, heavy loads for DB if you use Oracle DB Less appropriate: fast webservers as they use hard disks for several tiers, fast MySQL databases as the server is shared, auto-scaling functionality is not present.

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

• Installation and setup of VM Server are pretty straight forward.
• Many different guest operating systems are supported.
• There can be up to 128 virtual machines per physical server.

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

• Not as flexible as VMware.
• Could have slightly better templates for provisioning database nodes.
• In terms of performance it lags a bit behind Red Hat's KVM solution.

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

The ease of use on the Oracle platform is greater, flexibility and compatibility also helped in the choice, in addition to the cost-benefit.

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

• Migrating our workload from AWS to Oracle gave us a huge benefit in cost reduction.
• We've experienced a lot of outages.

Incentivized