Another week, another weekly digest. See what our authors are covering this week below.
Observability Tools: Getting to the Why In Your Prod Apps
Observability is a somewhat recent addition to the ever-growing list of buzzwords in the tech industry. However, unlike many of those items, observability does refer to an important concept—namely, the ability to understand a system’s internal state by looking at external signs it emits. This post is about how to achieve observability, including tools you can leverage, but we can’t talk about that without defining it and explaining why you would want to achieve it in the first place. So, that’s exactly what we’re going to do. Find out more from Carlos Schults on Scalyr’s blog.
People, Process, Technology: The PPT Framework, Explained
The people, process, technology (PPT) framework has been around since the early 1960s. Most businesses used it to improve the operational efficiency of their employees and tools. In the late 1990s, it was popularized in the infosec world by Bruce Schneier. These days, most software companies use the framework for information technology management. Find out more about it from Aditya Khanduri on Plutora’s blog.
A Practical Introduction to the Technology Acceptance Model
Before you impose a set of tools on your teams, certain considerations have to be taken into account. To start with, how effective are the tools at handling the tasks you have in mind? Then there is the issue of the actual users. Are they keen on taking up new tools? Workplaces often comprise different teams, all of which have staple applications they use to get work done. The tools your software development herd uses can be completely out of phase with those in the finance department. Learn more from Taurai Mutimutema on Plutora’s blog.
Serverless Deployment: How It Works and Practical Examples
We also updated a post on serverless deployment this week. Serverless deployment is the latest trend in the cloud arena. You have your code available, but it’s only executed when a request is made for it. It’s all provisioned within milliseconds and discarded afterward. You only pay for what you use. Sounds nice, doesn’t it? It’s also easier to update whenever you have to. So let’s take a closer look at how it works, what a deployment means, and a few examples. Check it out on Scalyr’s blog.