As an experienced Atlassian Marketplace Partner, Deiser has gone through different phases of the market, and by being so close to an important milestone about the Server deployment option, we wanted to share our point of view about four different aspects we think are essential to consider about your migration to Atlassian Cloud. In this blog post, you'll learn about insights on why opting for the Cloud is the best choice.
There are just over four months until Atlassian implements the end of support for the Server deployment, and many customers still need to decide whether to move to the Cloud or Data Center. On the other hand, many teams and companies are starting with Jira. Whether you're in the migration process or choosing which version of Jira or Confluence to acquire, this article is for both. From the perspective of an Atlassian Marketplace Partner, we'll explain why you should choose Cloud:
The tools from most software manufacturers have been active for over twenty years, have been hosted on customers' infrastructures, the famous "behind the firewall." On the other hand, with the explosion of cloud technologies these last ten years, new software manufacturers are 100% cloud-native while older manufacturers have had to move to the Cloud to stay in the loop with current manufacturers.
In terms of costs, a cloud product is infinitely more competitive than a "behind the firewall" deployment.
In terms of capability, there are currently a few things that can be done on the infrastructure that you can't do in the Cloud. Atlassian Cloud hosts a version of Jira, Confluence, Bitbucket, and more, available on a subscription model where Atlassian itself manages its deployment, maintenance, and operations.
At Deiser, we have been developing custom apps for Jira, Confluence, Bitbucket, and Bamboo since 2008. For the Marketplace, since 2012, it wasn't until 2015 that we began developing apps for Jira Cloud. Although the transition was challenging at the beginning due to the capabilities the Cloud option offered at that time, both in terms of features and performance, today, we prefer to develop 100% in the Cloud rather than on Server or Data Center for the following reasons:
In modern development, it's almost unthinkable to consider developing a product without user feedback, whether you are B2B or B2C. In our case (B2B), obtaining user feedback to enhance our products is challenging. Adding to this challenge, when developing on Server or Data Center and launching (for example) an in-app survey with a new release, it takes weeks or even months to start receiving responses. The reason is that we depend on the system administrators' time to update their instances. However, in the Cloud, if we want to gather feedback through an in-app survey, all our users can access the feature and survey within a day; that way, we get results almost instantly. Listening to the user is much easier in the Cloud than in Server or Data Center.
The same goes for data visualization and metrics. When we add a new event or property to the analytics tool for Data Center, it takes months to start gathering data that allows us to draw conclusions, whereas in the Cloud, we begin to obtain data immediately upon deployment.
This is an example of the workflow of the app we recently launched for project financial management called Budgety.
Getting insights and customer insights from Atlassian Marketplace apps is easier and faster in Atlassian Cloud.
In our team, we're enthusiasts of Agile and DevOps culture, and that's why we enjoy operating, monitoring, and controlling our systems. At the same time, as a challenge for technical excellence, we love a work environment that allows us to continuously integrate our code and deploy it daily, as many times as necessary, and automate it. Working on Server or Data Center requires dealing with multiple versions, branches, and environments. In contrast, developing in Cloud enables us to become a truly Agile team because we ensure the code integrated today is deployed today.
Deiser Product team is more Agile in Atlassian Cloud.
The Cloud security requirements for Marketplace partners are more rigorous as the stakes are more significant. When developing for Server/DC, you delegate a considerable part of the security to the customer and their infrastructure. When developing for Cloud, it's our responsibility; therefore, everyone else is protected by mitigating a security flaw reported by a customer.
On the other hand, it's much easier to participate in programs like Bug Bounty or hire a penetration testing service when in the Cloud. Additionally, Atlassian's security requirements for Cloud apps are much higher. In fact, they have an internal program called Cloud Fortified to ensure the apps' security, performance, and quality.
Projectrak is an Atlassian Marketplace app part of the Cloud Fortified program.
Reliability is another term demanded through SLOs by Atlassian in its Cloud Fortified Program. We cannot monitor in Server or Data Center because those services are "behind the firewall." However, in the Cloud, we have to take responsibility and want to. The team needs this information in a DevOps environment to prioritize potential issues detected in logs. Having firsthand access to all the information associated with system degradation or service interruptions is crucial for providing better support and reducing the time from problem detection to resolution.
This is the Status Page for Deiser's products:
The Deiser Product team works every day to create the best possible products for Cloud or Data Center. However, it's a reality that developing in the Cloud offers a series of advantages for manufacturers that allow us to have control and work on our apps' quality, security, and reliability. The dream of working in Agile environments becomes much more achievable when working in the Cloud.
No Comments Yet
Let us know what you think