Innovation drives success. And today more than ever, software drives innovation. No matter what product or service you offer, you’re a software company. You may not sell something called “software,” but successfully building, marketing, delivering, and supporting customers for any product today relies on software and technology. Innovation is what software developers do. And software developers are at the center of what CloudZero does.

“No plan survives contact with the enemy.” This is a famous quote attributed to the Prussian field marshal Helmuth von Moltke. It is also quite applicable to software development: “No code survives contact with the user.” In mission-critical environments, staggered deployments of software are a crucial part of controlled updates, designed to ensure maximum stability of production applications and services.

Managing stateful applications has been challenging for engineering and operations teams long before the debut of Kubernetes. In this post, we’ll explore all aspects of your deployments of stateful applications on Kubernetes, from the underlying hardware to Pod update strategies, and provide insights into how LogDNA uses stateful Kubernetes to build one of the world’s fastest log management platforms.

In our series on how to deploy an app to AWS with the least effort, we've talked about getting started, preventive measures, and securing your app. Today, we're going to focus on DNS (domain name system), specifically the AWS DNS service Route 53. As you're deploying your web app, you will inevitably use DNS.

The current period, with so many working from home due to the global Covid-19 pandemic, has seen a considerable increase in cloud communications consumption. Microsoft Teams’ daily active user count alone has more than doubled in approximately a month. As a long-time partner of Microsoft, Ribbon and our partners have been on the front lines helping organizations keep their communications robust and available during this time.

As a software producer, you need to keep releases moving, even as you need to move your technology ahead. Transitioning your Jenkins continuous integration (CI) pipelines to a newer, optimized system can’t be a roadblock, and your enterprise can’t afford the work stoppage a rip-and-replace rework would require. We understood that deeply when we built our CI/CD solution, JFrog Pipelines.