Honeycomb ruffled the first of many feathers nearly seven years ago when we coined the term “observability” in talking about production code. Today, we get to celebrate a major victory in our push for the term to break free from its unsuitable parent category, Application Performance Monitoring (APM).
Delivering dependable and high-performing IT services in 2022 requires coordination and collaboration across different workflows, areas of expertise, and even time zones. Whether serving in-house colleagues or external clients, there is immense pressure on IT management to create seamless experiences 24/7/365. Seconds matter when critical systems break down, and slow incident resolution can have costly ramifications on customer experience and employee productivity.
Last May, KubeCon gathered multiple tech enthusiasts, students, professionals, and companies. The event highlighted various topics and insights on how to collaborate on pushing the boundaries of cloud-native computin One of our Engineering Directors, Mykola Marzhan, shared his knowledge about databases on Kubernetes at KubeCon, during a session organised by the DoK.Community. We’ve picked out some of the key highlights from the talk below.
IT leaders, engineers, and developers must consider multiple factors when using a database. There are scores of open source and proprietary databases available, and each offers distinct value to organisations. They can be divided into two primary categories: SQL (relational database) and NoSQL (non-relational database). This article will explore the difference between SQL and NoSQL and which option is best for your use case.
In the previous blog, SQL vs NoSQL Database, we discussed the difference between two major database categories. In a nutshell, the main difference between NoSQL and SQL is that NoSQL adopts a ‘right tool for the job’ approach, whilst SQL adopts a ‘one tool for all the jobs’.
In addition to the usual updates to supporting utilities, Rancher Desktop 1.4 adds a couple of new useful features we think you’ll like.
The U.S. Army Combat Capabilities Development Command (DEVCOM) Army Research Laboratory (ARL) faces unique challenges in working with data to develop new technologies. It needs the ability to seamlessly analyze data both in the field and in the lab. Connectivity in the field can also be very unpredictable. Without a database that can handle intermittent connectivity, the systems become inefficient and waste time and money.
Back in late May, we hosted a webinar on the heels of our Series D funding announcement where we also took the wraps off our big product announcement: Cribl Search.
For this post, we’ll use a small Flask app that allows users to input a city name and they receive the current weather information for that city. We’ll make an API call to openweathermap.org to get the weather information for the city.
Breaking changes in production are inconvenient and can be costly to fix. Using commands like git clone < some GitHub repository >, executed on your terminal is a common practice, known as using the command line. This practice can be faster and more efficient than using a GUI. For this tutorial, I will walk you through the process of testing command-line applications git, explain why you need command-line applications, and describe in detail how they work.
