Operations | Monitoring | ITSM | DevOps | Cloud

DevOps-oriented engineers live at the intersection of IT operations and software development – understanding much of what it takes to maintain IT infrastructure while also being able to write code and deploy new services. DevOps-minded teams not only create services – but they also maintain them. A DevOps structure forces teams to take accountability for their applications and infrastructure instead of allowing developers to throw code over the proverbial wall to IT operations.

Continuous integration (CI) makes the cycle from design to code to building artifacts seamless and consistent. Continuous delivery (CD) makes delivery of that artifact to an environment the same every time. But, what about the actual environment the artifact is running in? Is it the same every time? That’s a hard thing to guarantee — unless you take advantage of an Infrastructure-as-Code (IaC) approach. This post explains how to use Infrastructure-as-Code to improve CI/CD.

Because DevOps practices can bring great speed and reliability to the software delivery lifecycle, release management can seem daunting. But, the improved visibility and collaboration brought about by DevOps can also help with the release management process. While the general concept of release management doesn’t really change between ITIL (IT Infrastructure Library) and DevOps, there are a few ways that the process differs.

Over the past few years, cloud computing has enabled agile, dynamic management of software and hardware components, on-demand. Nowadays, we can define our desired infrastructure in as little as a few lines of code, and we can provision real servers on cloud providers like AWS or Azure. Terraform is an open-source infrastructure-as-code (IaC) tool that has become the de facto solution for provisioning one aspect of those components.

IT teams are always under pressure to save money where they can, but doing so isn’t easy. Learn how one company was able to make practical IT wins that ultimately saved significant productivity loss and protected their bottom line.

OpenStack vs AWS is a discussion that almost every organisation must conduct when adopting a cloud strategy. This is because OpenStack and AWS are undoubtedly some of the most popular cloud technologies in both public and private cloud space. While AWS is the most popular commercial cloud platform, OpenStack remains its most popular open source equivalent. Both have their own pros and cons. But which one is better for you?

Logz.io is a SaaS (software as a service) provider with an observability offering made up of various managed open source technologies. These technologies include the Elastic Stack for logging and SIEM (security information and event management), Prometheus, for monitoring, and Jaeger for tracing. The company positions itself as an alternative to the Elastic Stack (or ELK Stack), which is made up of Elasticsearch, Logstash, Kibana, and Beats.

I recently wrote about the importance of logging and how developers often overlook it in the software development process. Now that you’re convinced that you should be logging throughout the SDLC, it’s time to choose a reliable and dedicated log management platform.

IT professionals love their metaphors. From “pets vs. cattle” to “post mortems” to “fog computing” and beyond, practitioners tend to use analogies to shape the way they think about complex technical topics. Here’s another analogy: Log looms.

At FlashDrive.io we use every day and love modern static websites frameworks like Gatsby, Hugo, Jekyll, and more. Gatsby, for its huge community and user base, is the first framework to have a complete build add-on developed on FlashDrive and we love playing with Gatsby every day (some of us are even a little too more invested in the project... we love you E, but get back to work!!). What's also great with Gatsby is that it comes with a large set of plugins to connect with various CMS.