One of the key pieces of wisdom regarding any kind of development project is that all software problems are inherently hardwaret problems. This is one among many reasons why devices like the iPhone and the Xbox have been so popular over the years. When software and hardware integrate properly, and code is written to specs that take full advantage of the platform, great things become possible.

Bugs are dumb. They’re also inevitable. However annoying that may be, it’s more productive to accept the existence of bugs in our workflows than to panic-spiral every single time they pop up. Part of the acceptance process is keeping bugs (or at least the ones you care to fix) top of mind by paralleling your error monitoring and your sprint planning.

There should be no doubt anymore that containers are revolutionizing the world of application development and leading the charge for purpose-built cross-cloud and hybrid-cloud topologies. There are other virtualization platforms that solved problems in server consolidation and data center optimization, but in the new world of cloud and mobility, proprietary monolithic middleware may have had its day.

Gatsby is currently generating a ton of buzz as the new hot thing for generating static sites. This has lead to a number of frequent questions like: A static…what now? How is GraphQL involved? Do I need to set up a GraphQL server? What if I’m not a great React developer, really more of a bad React developer?

When we talk about cloud providers, we often forget that not all data is the same — even in the same application, while we might think of this data as from a “financial application” or a “computation process”, the reality is that each data set has subsets upon subsets, and thus require specific applications to manage them.

It’s been a big month of great product updates in January, including the launch of the OpsRamp Winter Release, the ability to deliver collaboration across service delivery and IT operations teams with our certified ServiceNow integration and silver membership in the Cloud Native Computing Foundation (CNCF). In this month’s OpsComm, we’ll take you through some of the exciting news and updates at OpsRamp. To see all of the recent OpsRamp coverage, check out our newsroom.

The biggest challenge when a user complains of slow application is diagnosing why it’s slow: Is it due to a code-level issue or a database issue? Should we call the DBA or the application manager? Performance problems with the database can cause up to 70% of all application performance issues in production, according to consensus among database practitioners and experts.

When you are using Rancher to manage your Kubernetes clusters, at some point you will encounter the terms Rancher, RKE, and custom cluster. If you are new to Rancher, it can be difficult to understand the difference between and purpose of each of these concepts. In this post, I will go over what each component is used for and how they are used together in parts of the system.

After closing a $20 million Series A round, Mattermost is skyrocketing in popularity as a secure, open source Slack alternative for enterprise DevOps and IT. High-trust teams are adopting it for messaging to overcome some of the biggest collaboration challenges today.

Let’s start with the happy ending — after a long search, we managed to identify a Netty memory leak in one of our log listeners and were able to troubleshoot and fix the issue on time before the service crashed.