Operations | Monitoring | ITSM | DevOps | Cloud

In this article, I’ll provide a guide to Git for non-developers. So, if you are reading this as a full experienced Git user, you may disagree with some of my statements. Don’t bother reading on; we recognize you as the expert! If, on the other hand, you’re new to Git, this piece is for you.

At the end of 2021, we published a blog post about the Autumn budget in the UK, what it meant for IT teams in the NHS, and why data management should be prioritised. We looked specifically at four key areas for sharing, monitoring, protecting, and accessing data that we believe are crucial elements of the digital transformation journey. Digital transformation is part of the NHS Long Term Plan, a wide-ranging programme to upgrade technology and digitally-enabled care across the NHS.

This is the fifth part in the DevOps 101 series and it’s time to talk about automation. Before we get into it, I just want to recap what DevOps is. Microsoft’s Donovan Brown sums it up nicely in a single sentence: DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The important thing to remember here is the order in which he talks: people, process, and products. That’s the way DevOps works.

Interrupts are often seen as a problem that eats away at your team’s productivity, and gets in the way of shipping important things for your customers. It’s often consciously accrued from the tech debt we accept to ship features sooner. However when a team doesn’t have a good strategy for dealing with the consequences of those decisions, the pain is felt much more acutely and much sooner.

Aiven for OpenSearch® On 2022-08-23, Aiven will complete its migration away from Elasticsearch. Read on to find out how this affects the backwards compatibility we were providing.

Data disasters are practically inevitable, but a planned out backup strategy can combat their damaging effects. The Cybersecurity and Infrastructure Security Agency (CISA) of the U.S. government is a major organization that recommends sticking to a 3-2-1 backup strategy. Follow the 3-2-1 backup rule to ensure that your data is kept safe.

As a managed service provider, your success depends largely on the satisfaction of your customers. If they’re happy, they’ll stay with you and recommend you to others. But if they’re not, they’ll take their business elsewhere. Sometimes, some customers are never satisfied no matter how hard you try. Instead, they’re always finding something to complain about, which can be frustrating.

The demand for cloud services is rising. Databases have been popular tools for a long time. However, the landscape is changing, with cloud databases becoming increasingly popular.

InfluxDB has over a dozen different client libraries to help developers work with time series data in whatever programming language they like best. The Python client library is one of our most popular options. It’s simple to learn, and working with InfluxDB in a language you’re comfortable with helps you get started doing powerful time series analysis quickly.

This is the second post in a 2 part blog series on debugging, monitoring and tracing NodeJS Lambda applications. If you haven’t yet seen part 1, check it out here (it’s a great read!) Now let’s get back into our post with one of the most commonly experienced issues when it comes to Lambda functions, Cold Starts.