On December 3rd, the Elixir core team announced the latest Elixir release, 1.13. In this post, we'll explore some of the more exciting changes and new features, and discuss their impact on the Elixir community.

In this post, we will explore memory heap allocation in Node and push local hardware to its limit. Then we will find practical ways to monitor Node processes to debug memory issues. Ready? Let’s get going! To follow along, you can clone the code from my GitHub.

Elixir provides a very powerful suite of tools that devs can use to observe the behavior of their code and debug errors. There are several different strategies you can use to debug code in Elixir. While it is hard to produce a comprehensive list of all possible debugging methods, we will cover some of the most common methods in today’s post.

Performance is one of the most important aspects of web application development. A fast application will make its users, developers, and business stakeholders happy, while a slow one is sure to frustrate all three parties. In this article, we will consider some practices that you should adopt to scale your Node.js servers. Your servers will then be able to handle high traffic workloads without a degraded user experience.

It is vital that you understand how garbage collection works in Ruby to stay in complete control of your app’s performance. In this post, we will dive into how to implement and customize garbage collection in Ruby. Let’s get going!

Welcome back to this final part of our four-part series on metaprogramming in Elixir. Previously, we explored the various applications of macros. In this part, we’ll delve into common pitfalls that you might encounter when metaprogramming in Elixir.

Artillery is an open-source command-line tool purpose-built for load testing and smoke testing web applications. It is written in JavaScript and it supports testing HTTP, Socket.io, and WebSockets APIs. This article will get you started with load testing your Node.js APIs using Artillery. You’ll be able to detect and fix critical performance issues before you deploy code to production.

Error handling is one section of our job that we tend to neglect, especially when working on something new, interesting, or something we just need to get working. We’ll handle errors later, we say — and that’s often a big lie. But that’s not even the worst part. The problem comes when we decide to ‘quickly’ add some code to handle our errors and completely forget about the importance and relevance of a properly constructed error message.

Authorization (not to be confused with authentication) is vital to every application but often isn’t given much thought before implementation. The IETF Site Security Handbook defines authorization as: So, in short, authorization is about defining access policies and scoping. For example, consider a platform like Github.

Node.js v17.0.0, the latest major version of the popular JavaScript runtime, has just been released. It supersedes v16 in the Current release line of the runtime. V16 is now in line to be promoted to the long-term support (LTS) channel on October 26, 2021, as it’s an even-numbered release. Despite being a relatively minor update, this release brings several refinements to the runtime, including more promisified APIs, JavaScript engine upgrades, and OpenSSL 3.0 support.