GitHub vs. IBM PowerVM vs. Kubernetes

GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.

Incentivized

IBM PowerVM only is available on IBM POWER machines. It makes live much easier, compared to bare metal machines (OPAL) or machines with KVM. Personally I would not like to manage systems that don't have IBM PowerVM. The current line-up always includes IBM PowerVM (firmware built-in).

Incentivized

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

• Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
• Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
• Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.

• IBM PowerVM is used for virtualization on IBM Power series hardware to utilize the hardware resources more efficiently like micro partitioning for CPU, NPIV for fibre port...etc
• IBM PowerVM provides the feature of live partitioning mobility (LPM), which allows moving the running virtual machine from one hardware to another hardware without any disruption on a virtual machine.
• IBM Power VM provides the feature of Integrated virtual manager (IVM), which helps to manage the single IBM Power hardware. There is no need to purchase a separate hardware management console to manage the Power hardware. This works well for small organizations having small environments.

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

• Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
• Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
• Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
• While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.

• The ability to run Windows. Hardware architecture does not allow this, but it is a limiting factor.
• More performance monitoring and management could be built in.
• Sometimes is marketed and packaged in some rather unusual ways

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

GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.

The product works. It provides the proven environment to support IBM's primary operating systems that run on the IBM Power processing systems. This by extension includes the IBM various storage products that work within that environment. It has proven to be seamless as the environment has grown and as various new products and version updates have been added. As with most IBM products, the support is excellent.

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.

GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.

Incentivized

Since it is built into the firmware (hardware) it requires no separate installation (except for the Virtual I/O servers, if you need those). Both HMC and Novalink (with PowerVC) support IBM PowerVM well and offer a user-friendly interface to setting up LPARs and making changes, most on the fly. Modern systems also give insights into performance, power consumption etc. A lot of separate tools exist to show more details, like LPAR2RRD, IBM Instana, IBM Turbonomic etc.

Incentivized

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

There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.

Incentivized

While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.

Incentivized

Our company utilizes VMware and PowerVM. VMware is very user friendly from an IT support view and makes supporting Windows OS easier. PowerVM is moving in that direction. PowerVM is better in that you can prioritize workloads across different VMs and be granular in your reservation of cores and virtual CPUs. PowerVM allows you to modify VM characteristics while the VM is up and running

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

• Team collaboration significantly improved as everything is clearly logged and maintained.
• Maintaining a good overview of items will be delivered wrt the roadmap for example.
• Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.

Incentivized

• We are able to run several LPARs on one frame, which means we do not need to buy as many physical servers. That saves on floor space, power, and heating and cooling of the data center, among other things.
• Using LPM allows us to do maintenance on a frame without impacting the LPARs, giving us greater uptime.

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