Operations | Monitoring | ITSM | DevOps | Cloud

With support for Atlassian Server products ending in February 2024, many of you are likely evaluating or planning your migration to Bitbucket Cloud. To help you navigate the migration process, we've put together a list of frequently asked questions that we hear from customers. Each section below has several resource links to help you learn more and start planning your migration.

The early days of cloud computing saw people subject it to severe scrutiny. The main talking point revolved around its security and the ability of infrastructure providers to keep it secure. Regardless of the doubts, more businesses are migrating to the cloud. That's mainly because leading cloud service providers have consistently improved and upgraded their processes to secure their networks. However, even with years of improvement, the old fears remain.

At Upsun, we are committed to making your site perform as best as possible. As part of this commitment, we need to smooth down the system load spikes as much as possible—especially when many crons are triggered at the same time on a particular Grid region. To do so, we are increasing the default cron jitter from five minutes to 20 minutes.

One of the things we love about working in the cloud is the ease and scalability it brings to application development. It enables us to build out applications, APIs and any infrastructure that is needed from prototyping an idea, through to self scaling deployments. Monitoring and troubleshooting production-level serverless applications is always tricky, Especially working across a number of services and the many logs they can produce.

With more than 7,000 customers and double the number of employees ServiceNow had four years ago, our digital technology (formerly IT) operations team faced increased demand for compute, storage, and bandwidth. At the same time, we had to maintain tight security controls. We embrace a three-zero strategy: zero unplanned outages, zero physical footprint, and zero user-reported incidents.

Edgardo Peregrino is a freelance software developer, writer, maker and IT technician. For six years now, I’ve been a passionate maker with a focus on robotics. Recently, I entered the world of cloud native computing, which has allowed me to integrate maker projects with open source tools such as Grafana, Prometheus, and Jaeger.

Continuous integration (CI) / continuous delivery (CD) is a model that allows software development teams to automate the integration and delivery of code changes in a more frequent and reliable manner. This gives development teams more time to improve the quality of their code, test with greater depth, and leads to more customer deployments overall.

We have a term we like to use when we meet CFOs who have just gotten their biggest AWS bill ever: bill shock. Bill shock is when finance suddenly rings the alarm that the bill is “too high” and gets everyone scrambling to explain what they’re spending money on. It often happens when the bill reaches a new milestone (the first million, ten million, or hundred million) or growth trajectory (it doubled in a quarter!?). The problem with bill shock is that it can be highly disruptive.