Let’s talk about the world’s currently trending topic for a second: AI. Now, before you click out of this blog, sighing to yourself that this is yet another blog that wants to tell you how to write code with ChatGPT; bear with us. As almost everyone has used some form of AI – especially ChatGpt – to help them with some form of a task, we can all agree that it’s quite an interactive experience.

If you’ve ever been enraptured by the magical world of gaming, you’ve likely encountered Blizzard Entertainment. Known for its high-octane, immersive games, Blizzard has long been a beacon of quality in the gaming universe. Their latest offering, Diablo 4, has taken the gaming community by storm, breaking records and setting new standards for commercially and technically successful game launches.

Unless you live under an actual rock and haven’t hauled yourself into modern times, I’m sure you know – and most likely use – JavaScript. You know, the versatile and dynamic programming language that powers the web and beyond. From client-side scripting to server-side computing, and even robotics, JavaScript is everywhere. However, like any good craftsperson, a JavaScript developer knows that their work is only done once it’s been tested.

A paradigm shift is overdue in the realm of software observability. While Site Reliability Engineers (SREs) have been having fun with metrics, traces, and logs, software developers have been left in the lurch, shackled to the conventional, low-fidelity tool of logs. Why should SREs have all the fun, right? Welcome to the dawn of a new era. An era where developers, too, can enjoy superior observability engineering. That’s where the fourth pillar of observability comes in: Snapshots.