Atlassian Bitbucket vs. Azure Kubernetes Service (AKS)

As a team we need to push code into the repo on daily basis, Bitbucket has proven that is a reliable and secure server to save and get the code available in no time. The administration part is really easy and there's an extra tool for every developer profile either if you want to use the console or a GUI like Sourcetree.

Incentivized

AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.

Incentivized

• Very easy to integrate with other DevOps tools like Jenkins and with project/workflow management tools like JIRA.
• Very efficient in managing security and compliance standards for code, especially during pull requests, merge requests, branching, etc.
• Very robust in performance, especially the cloud and datacenter versions hardly hit any performance issues and supports more than 2000+ developers in my company.

Incentivized

• AKS makes it easier to replicate data to multiple regions
• Azure portal make it easier to manage the resources of the organization

Incentivized

• The code management UI is a bit rough around the edges and difficult to work with.
• BitBucket does not have the same simplified PR management tools as other competitors.
• It's not as easy to integrate 3rd party apps as other competitors.

Incentivized

• Steep learning curve
• Expected charges are unclear until you see real production usage
• Operations teams need to learn an entirely new skill set

Incentivized

All products have room for improvement. The system improves over time with better and better integrations and I look forward to even more features without paying extra! The system has increased transparency across my organization and with this transparency comes increased throughput on projects. I don't think I can go back to any other system and we are definitely married to this product.

Incentivized

The architecture of Bitbucket makes it more easily scalable than other source code management repositories. Also, administration and maintaining the instance is very easy. It integrates with JIRA and other CI/CD applications which makes it more useful to reduce the efforts. It supports multiple plugins and those bring a lot of extra functionality. It increases the overall efficiency and usefulness of Bitbucket.

Incentivized

As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.

Incentivized

The customer support provided by Atlassian (Bitbucket's parent company that also makes Jira, Confluence, etc.) is very helpful. They seem to be very concerned about any issues reported with their products and even just questions about functionality. They are constantly improving the products with new features in nearly every release. Plus they have a plethora of online documentation to reference.

Incentivized

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more familiar tool compared to GitLab. Bitbucket won out because of its close integration with Jira and being in the Atlassian family. It was also cheaper than GitHub. As we started with Jira, Bitbucket addition became a natural next step for us. We really liked Bitbucket and stayed with it but we do know we have great options in the form of GitHub and GitLab should we need to scale fast.

Incentivized

Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.

Incentivized

• It's allowed for a lot of automation in terms of development workflows. It lets us pursue CI/CD approaches and get releases out faster
• It has let us get our infrastructure configuration into VCS, which further improves our automation abilities.
• It has aided in keeping track of changes, and allows us to keep workflows organized so we can track the status of development

Incentivized

• We had to spend more time on Azure Kubernetes Service (AKS) than on AWS and GCP to get our kubernetes cluster up and running
• The resources on nodes need to be left out unused, so effectively it is wasting money there
• It definitely made us spend more time into maintaining kubernetes

Incentivized