🙂 What is Observability Driven Development ?
Development is kind of like an iterative process. You write some code, you make some changes and then you try to execute it. After execution you try to analyze the result and sometimes you find that it is not working how it is supposed to be working.
At that point you try to fix the problem by making more changes and then you do another iteration until you solve the problem. The main point of observation driven development is to make those iterations more efficient.
🤔 What is the need of ODD ?
- We are using the same old traditional methods for debugging like console logs and stuff. But those methods are not good enough for heavily distributed environments.
- Imagine using those methods on a microservice platform. It will be difficult to keep track of things.
- Observability driven development empowers developers to be more data-driven instead of working arbitrarily, just running a test and seeing if it passes or not. It makes developers more aware of what they are trying to find out and deepens the understanding of the effects of the changes they are making.
😮 Benefits of ODD
You can save your time by using telemetry data to find out what went wrong and how can you fix, instead of wasting your time seeking out why the application doesn't work.
You can improve the efficiency of the development cycles by analyzing observability data in forms of traces, metrics and logs instead of raw data.
⭐ What is Sprkl ?
- Sprkl is personal observability platform. Sprkl is an extension for Visual Studio Code. It is built to provide observability data right inside your IDE. You can install it via the Visual Studio Code marketplace. It's completely free.
⬇️ After installation
- Sprkl comes with both Jagger and OpenTelemetry. You can instrument your application with a single command and once you run it, it will provide you with different kinds of observability information right inside your IDE.
✨ Features
- Code level traces - help you understand precisely how your recent code change executes.
- Interactions - help you see how your code change plays with other entities in the system.
- Coverage - helps you determine how much of your recent code change is covered by existing tests.
- Insights - help you improve your code performance by getting runtime feedback.
You can watch Kunal's podcast with Erez Voitiz on YouTube
You can watch demo on YouTube.
You can join free beta by visiting the official website.