Operations | Monitoring | ITSM | DevOps | Cloud

In software development, processing and storing data in different states reflects the business rules an application is built on. The heart and soul of any software application is the data that is persisted in databases for retrieval and further processing. The database system (SQL or Non-SQL) chosen for an application must serve the required data processing and storage needs of the application.

The container ecosystem is moving very fast and new tools designed specifically for Kubernetes clusters are introduced at a very fast pace. Even though several times a new tool is simply implementing a well-known mechanism (already present in the VM world) with a focus on containers, every once in a while we see tools that are designed from scratch rather than adapting a preexisting idea. One such tool is Komodor.

A dark launch is a deployment strategy for testing new versions of a service in production. When running a dark launch, you deploy a new version of a service and route a copy of production traffic to it without returning responses to users. This lets you see how a new version of a service handles production load, watch for errors, and compare performance between the old and the new versions—without affecting users.

At Redgate, we strongly believe that all databases should be managed and orchestrated in the same way, with the same standards of security and quality in releases. For the past few years, we’ve been leading the adoption of database DevOps by focusing on the most challenging parts of the process like version control, continuous integration and making deployments consistent, predictable and repeatable.

This blog is the first in a four-part series on infrastructure automation for government agencies that are modernizing digital systems while grappling with budget and staffing constraints and the challenges of COVID-19. The last 12 months have been a turning point for many government agencies. The COVID-19 pandemic has accelerated the drive towards modernization and, with it, the need to ensure security and compliance requirements across a host of legacy systems and processes.

Virtual machines (VM) offer great flexibility for hosting web applications. A developer/engineer is able to configure and control every piece of software and every setting that the application needs to run. Azure, one of the largest cloud hosting platforms, has virtual machine offerings for both Linux and Windows-based operating systems. In this tutorial, you will learn how to set up a continuous deployment pipeline to deploy a Node.js application to an Azure virtual machine.

There’s a big difference between the MySQL database powering your internet of things (IoT) lightbulb and the one powering your website. There’s a chasm between the SQL Server Express database in your lightly used application’s VM and the monster multi-region SQL cluster you have running on Microsoft Azure. This kind of database diversity is everywhere today. But what are the differences between these databases, and how can administrators justify database spend?

First, thanks for indulging the clickbait title joke. Serialization is the unsung hero of harmonizing network and application relations and deserves the occasional, snarky callout. Moreover, identifying how the unique mix of network clients in your environment consume your carefully manicured infrastructure is critical for managing network cost. Because today, a rapidly expanding, diverse pile of new technologies all assume the network is a magic grid, no tuning required.