Scalability isn't just a buzzword; it can transform modern business operations. Let's explore what scalability means in the context of DevOps and why it's a crucial factor in achieving success.

As organisations increasingly embrace cloud computing, one common misconception is the idea of "building data centres in the cloud". In this blog post, we'll explore why building data centres in the cloud is not the right approach and what alternatives are more suitable.

Despite investing time and resources in DevOps practices, you might be wondering if it’s paying off. Here’s why a State of DevOps report can be a game-changer for CTO’s seeking clarity and direction:

As HashiCorp’s 2023 State of Cloud Strategy Survey reveals that a staggering 94% of organisations are still wasting money in the cloud, we follow up on our previous blog post on how to reduce your cloud spend.

Is your DevOps team not quite hitting the mark? Let's delve into the common pitfalls that can hinder your DevOps initiatives. From misaligned strategies to inadequate tooling, understanding the reasons behind your team's challenges will set the stage for improvement.

One theme tends to surface quite often in discussions with technology leaders in the beginning of their cloud journey: “We’d like to use Infrastructure as Code, because it helps us become cloud agnostic.”
Unfortunately, this is usually not the case.

When considering cloud-native technologies, one of the most common concerns of technology leaders is ‘vendor lock-in’. In the world of cloud, vendor lock-in typically means building a product or a SaaS application using cloud-native technologies that are only available on a certain cloud provider.

As a technology leader, DevOps and cloud engineering are likely to be central to your organisation's success. As DevOps is playing an increasingly crucial role, staying informed about the latest trends and best practices is essential.

Releaseworks, the trusted DevOps and cloud engineering partner for the world’s leading software engineering teams, has today appointed Eamus Halpin as Fractional COO. Mr Halpin also joins the Releaseworks board of directors.

Unless you know what to improve, every change you make is just shooting in the dark. This is why feedback loops are so important - the faster you know if something works or not, the sooner you can point your efforts in the right direction.

In the world of two and three-letter acronyms, it’s easy to get lost.

Here are the DevOps terms and acronyms all technology leaders should know:

In our experience, one of the most successful DevOps methodologies is creating cross-functional development teams who own their product from ideation to production. I think everyone in your development team should know DevOps. Here’s why:

I like to say “if you speak with a hundred people about DevOps, you’ll get 100 different opinions of what it is”. For us at Releaseworks, DevOps is first and foremost a way of working.

With a handful of strong cloud providers on the market, more and more teams are choosing to deploy their products on multiple platforms. While high availability is a goal for some, many more are choosing a hosting approach to take advantage of combining the benefits of different platforms. In this blog post we explore the various options available, and typical use cases for them.

Ask any established software delivery team about what’s slowing them down, and one topic that is bound to come up is “environments”. Whether there are too few of them, or they are vastly different from each other, environment-related issues tend to be the #1 cause for unexpected bottlenecks in the software delivery lifecycle of modern web applications. It is also a fact that for many teams, more than half of the total cloud spend is on testing environments.

The beginning of the year tends to be a busy time for information security professionals, and this year is turning out no different: the CircleCI breach over the holiday period is making waves among companies using the platform, and anecdotal evidence suggests that phishing attackers are expectedly taking advantage of staff members returning from the extended break. Therefore this is a great time to consider implementing the three easiest security controls for your AWS platform.

A healthy DevOps culture is one of the key ingredients of high-performing software teams.

Here are some signs that you’re doing it right.

A robust incident response capability is key for any web application product team who takes their craft seriously. Whether it’s an incident affecting the stability, availability or reliability of the product, the speed and expertise with which it is resolved makes all the difference in keeping your customers happy. Then there are other operational incidents, like information governance or cybersecurity incidents, which you simply cannot afford to get wrong. In this article we’ll explore three steps to take to improve your incident response capability.

Traditionally, many organisations have interpreted the DevOps ‘shared responsibilities’ principle to mean that the developers in your team should man the 24/7 out-of-hours schedule in addition to their daytime duties. This approach does have its benefits: getting developers to feel the pain of running the product first hand is a sure way to ensure operability is front and centre in sprint planning conversations. Plus, who is better positioned to deploy a hotfix overnight than your lead developer?

With cybercrime on the rise, it’s imperative that businesses take the necessary steps to secure their data and workloads. Amazon Web Services (AWS) provides a suite of powerful security tools to help protect against malicious actors. In this article, we’ll take a look at the top three AWS security tools that you should be using right now to protect your cloud infrastructure. From real-time security posture management to API resource logging, these tools will help you ensure your data and workloads are secure. Let’s get started.