GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
IBM Cloud Object Storage
Score 9.3 out of 10
N/A
IBM Cloud Object Storage is an IBM Cloud product in the endpoint backup and IaaS categories. It is commonly used for data archiving and backup, for web and mobile applications, and as scalable, persistent storage for analytics.
$0
per month
Kubernetes
Score 9.0 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
GitHub
IBM Cloud Object Storage
Kubernetes
Editions & Modules
Team
$40
per year per user
Enterprise
$210
per year per user
One-Rate Plan
As low as USD $12/TB a month
per month
Standard Plan
Free up to 5GB—no minimum fee, pay only for what you use
per month
No answers on this topic
Offerings
Pricing Offerings
GitHub
IBM Cloud Object Storage
Kubernetes
Free Trial
Yes
No
No
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
Optional
No setup fee
Additional Details
—
The One-Rate and Standard service plans for Cloud Object Storage include resiliency options, flexible data classes and built-in security. Pricing is based on the choice of location, storage class and resiliency choice.
—
More Pricing Information
Community Pulse
GitHub
IBM Cloud Object Storage
Kubernetes
Considered Multiple Products
GitHub
Verified User
Director
Chose GitHub
GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular …
Mostly cost because most of them deliver a similar product and the decision for a hyperscaler (when you do not plan to use Multi Cloud) was not solely based on the object storage offering. Moreover, other components as K8s/postgres and the overall picture inclunding consulting …
Amazon S3 has a more complex pricing model. It charges as per the requests, which will be more costly for us compared to IBM cloud object storage. The safety of our data is the main focus, and this is guaranteed with IBM.
IB cloud storage offers more options than what is offered by AWS cloud storage
Verified User
Engineer
Chose IBM Cloud Object Storage
I feel that both of these products have almost the same kind of work. Both are used for cloud based storage of unstructured data. IBM Cloud Storage Object Storage provides an upper hand as it is more effective.
We already had an enterprise Kubernetes 8 set up, so once we got our namespace it took me about 2 weeks to go from not knowing anything to having a self-contained jar in a container, running on Kubernetes 8. In comparison, it took me two weeks to install Java on a blank server …
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.
In my experience, IBM Cloud Object Storage is well suited for projects like the one I am working on. This includes the use of natural language classification and the uploading of data to train a machine learning model for tag suggestions based on a body of text. Using IBM Cloud Object Storage has helped with this greatly. IBM Cloud Object Storage has also been great for Big Data Analytics thanks to its scalablilty and ease of use for large datasets. Alongside IBM Watson and our team's internal big data tools we've managed to process and analyze data more efficiently, leading to key insights that have driven business value for our clients.
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.
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 Cloud Object Storage is an excellent choice for disaster recovery and backup solutions. Its high durability and geographic redundancy ensure that our backup data is safe and can be quickly restored in case of a disaster. This capability is crucial for maintaining our business continuity and minimizing downtime. We have deployed our loads in an IKS cluster distributed in 3 different AZs with stateful data allocated in COS.
We have a video streaming application and need to store and deliver a vast library of video content to millions of users worldwide, so we store our data in COS, which is cheap and reliable.
We have a bunch of data that must be analyzed and stored in datasets for fraud detection, risk management, and customer insights. In these cases, this data is moved from Onprem to IBM Cloud so we can use cheap storage like COS.
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.
Searching and retrieving—full-text search or metadata search—is one of the significant areas of improvement. It isn't easy to search for data with this.
Integration with other IBM cloud services is trickier. For example, integrating this with API Connect to access the data from API will be difficult for users.
Support - I think you should have more support community.
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.
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 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.
For my use cases, it has been a very smooth experience. Even my new colleagues have been able to get on top of things very quickly. This shows how easy it is to work with
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
We rarely face downtime or access issues with IBM Cloud Object Storage. It’s mostly available when we need it, even during peak hours or heavy data loads.
I would give it a 9 because it works smooth with our AI and analytics tools, no major slowdown. Pages and dashboards load fine most of the time, and reports finish in decent time even when data is heavy.
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.
I have been working in IT sector for more than 15 years. I have worked with various vendors. IBM's sales team, support team have been really helpful. After we start to use their product, their UX design team also contacted us to get feedback from us. They are really interested about our experience.
I just researching and applying the tools on their platforms to ensure a good learning path, based on my needs. Reading the documentation related with resources, tools. Is too big, but I am trying to know more about it every day. It is a good way to know more about their resources. A new way to attract new customers. At the end of the day, we are all involved in improvement and automation of our tasks and resources for customers and end-users.
Yes Our organization used IBM professional services to implement IBM object storage because of its data consistency and multiple way to upload and download data and its encryption security features. Also that its brand matter for the any organization to secure the layer and storage. It sis also verify that application and system are compatibale for this product
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.
Amazon S3 is a great service to safely back up your data where redundancy is guaranteed, and the cost is fair. In the past I have used Amazon S3 for data that we backup and hope we never need to access, but in the case of a catastrophic or even small slip of the finger with the delete command, we know our data and our client's data is safely backed up by Amazon S3. Amazon S3 service is a good option, but based on the features it provides compared with IBM Cloud Object Storage, it is less suitable. IBM Cloud Object Storage is also integrated with more services, like IBM Cloud SQL and IBM Aspera, which AWS does not provide to transfer files at maximum speed in the world.
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.
Scaling up the number of users can lead to significant increases in licensing costs, which, while not a technical limitation, can be a practical constraint for some organizations
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.
This allows us to recommend a platform to our clients that will quickly help them create new, efficient business processes with very little development.
This saves clients hours and days of manual analysis of images, allowing the system to do the work when attaching Object Storage to models.
There is a learning curve in utilizing the storage and the modeling, but once up and running, it works well during deployment.
