This article is a follow up of our previous article where we explain how we deployed a Kubernetes cluster with k3s on a Raspberry Pi cluster.

Some time ago, the Register published an article titled “Lambda and serverless is one of the worst forms of proprietary lock-in we’ve ever seen in the history of humanity”. It received a lot of attention, and vendor lock-in has become a perennially popular question at conferences. But I’m here to tell you that you are probably thinking about vendor lock-in all wrong when it comes to serverless.

Microservices and containers multiplied the complexity of Ticketmaster’s software system. Its engineers solved their debugging problems with Jaeger, an open-source tracing tool from Uber incubating at CNCF.

One of the most common complaints I hear from managed services providers is how hard it is to recruit staff. In the past month, I’ve had three MSPs ask me: With the high cost of tech talent, how can I afford to fill technical and managerial roles? When’s the right time to employ an extra tech? Why am I struggling to grow my team?

These days we spend a lot of time talking about modernizing our stack, modernizing our architectures, using new application components, modern application life cycles, etc. So, what is this all about and why do we spend so much time talking about it? First, there is a lot of self-serving vendor speak involved…starting with cloud providers and closely followed by open source commercialization shops and commercial ISVs (ourselves included) who have to spin the world in their own image.

When it comes to monitoring your user experience, it is easy to monitor and optimize just the landing pages. But, does your user’s journey end at the landing page? No. Monitoring your user journey goes deep. Each click the user makes on your site or service needs to work and be as fast and responsive as the initial page load.

Thousands of developers work in Raygun every day. But as the number of team members added to your organization grows, it can be tough to make sure only plan Owners have access to major plan settings in Raygun. Starting today, if you are a plan Owner, granular permissions will help you gain more control over who has access to key Raygun settings at the product, app and plan level.

Making Node.js applications quick and sturdy is a tricky task to get right. Nailing the performance just right with the V8 engine Node.js is built on is not at all as simple as one would think. JavaScript is a dynamically typed language, where you let the interpreter assign types to variables. If you’re not careful this can lead to memory leaks.

What is the most important feature your Node.js application can have? Do you think it’s having fancy fuzzy logic for your full-text search, or maybe using sockets for real-time chats? You tell me. What’s the fanciest, most amazing and sexy feature you can add to your Node.js application?

Node.js monitoring is a tricky task. There are certain challenges to look out for. Because Node.js is a dynamically typed programming language and single-threaded you give the interpreter and runtime a lot of freedom to make decisions. This can easily result in memory leaks and high CPU loads. Parallel execution is simulated in Node.js by using asynchronous execution of functions. But, if a single function blocks the thread or event queue, the application performance will take a huge hit.