Performance issues never seem to disappear from the world, no matter how fast new computers become. To deal with those issues we need proper tools. We have some great tools on Windows. On .NET Core with Linux, things are not so great. But they’re getting better.
.NET Core 3 was recently released and brought with it a bunch of innovations, including a brand new JSON (de)serializer System.Text.Json. We’re going to compare this serializer with Newtonsoft.Json and other major .NET serializers. Check out this epic performance battle.
So you’ve decided to create a web application? Great, welcome to a world without any easy choices. There is a vast amount of different great technologies in every step you are going to make. And for every option, you will find a notable company that used it with great success. We’ll go through 9 must decisions you have to make…
There’s an incredible built-in mechanism in Windows called Performance Counters that allows you to follow a whole lot of useful metrics. It’s easy to use, comes free, and perhaps not used as much as it deserves. In this article, we’ll see how to monitor performance counters with PerfMon, …
In the 3rd part of the series we’ll see how to create asynchronous steps in the pipeline with TPL Dataflow. We’ll also see a new implementation using the Disruptor-net library.
Logging is a big part of software development for many years now. This guide is a bird’s eye view of modern solutions for logging in .NET space.
One of the most important concepts in modern programming is Exceptions. They were introduced in the 60’s with LISP and eventually made their way to practically all modern programming languages. This article is an extensive guide to dealing with exceptions in Visual Studio.
In the First Part of the series, we talked about the Pipeline Pattern in programming, also known as the Pipes and Filters design pattern. In this part, we’ll see how to implement such a pipeline with TPL Dataflow.
The Pipeline pattern is a powerful tool in programming. The idea is to chain a group of functions in a way that the output of each function is the input the next one. The concept is pretty similar to an assembly line where each step manipulates and prepares the product for the next step.
I’ve been developing software for 10 years now. Every now and again I wonder what it is that makes me tick. What’s the element that makes me come to want to go work in the mornings. In other words, what is it that motivates us as software developers?
Don’t know about you, but I’m obsessed about performance. I’ve gathered a list of 10 best practices on dealing with performance problems, starting with when you need to deal with them at all.
LINQ is terrible to debug. We have no way of knowing what goes on inside that query. We can see the input, we can see the output, but that’s about it. What happens when something goes wrong? Do we just stare at the code, trying to get some kind of insight? There’s got to be a better way…