Sometimes we have too many business data to process that even improving the algorithms and using strategies like threads seems to be not enough to complete everything on schedule.

The data processing strategy using “more than one computer” is not new at all. But there’s times when we lack the idea of “how can I use this kind of thing on my project”.

Below I will explain the overall idea, tools and the strategy itself. Then, I will provide an example using C#, Postgres and Docker.

Disclaimer: it’s not a framework, it’s not the fittest approach of anything. It’s just…

It’s still a monolict, but it’s get better.

There’s a lot of recipes to improve performance on every single system. Cloud is not new anymore, distributed systems became closer of every single task inside systems of any size. But, until we get there. There’s some tips to improve the time spent processing any kind of data.

The strategies that I try to explain here, in this post, can be applied on many scenarios, but sometimes the explanations are biased on my daily basis activities, that normally include something like: well, we improved the algorithms the best we could but, can we distributed it in order to process the…

The algorith complexity is the base of algorith performance but, there are planty of other problems that need discussions.

One of them, I personaly call “the jumping problem”, that in fact you, software developer, probably already know and probably have experienced.

The jumping problem happens when you call something like database, files, APIs, libraries and even your own “heavy” functions outside of you core application too many times inside your bussiness logic.

There is no receipt for performance, when you have this kind of problem many things should be studied, but in many cases call too often something “outside” your…

Not so focused on development itself, this post has a very specific purpose:

In a SQL Server database where Microsoft Dynamics AX 2012 is running, all connections originate from AOS and, consequently, a user normally called “svc.aos”. Thus, it is difficult to collect all the “context” related to the database and responsible user at once.

As a context, we can understand things like: query, execution plan and duration.

There is a stored procedure that, in a synthetic way, is capable of presenting various information with a simple execution. It is sp_WhoIsActive.

However, as it is only focused on SQL Server…

As first post, I decided to write about asymptotic analysis, a topic that, in my opinion, should be a basic knowledge for every software engineer.

So, instead of base this post on several books, references, or even to many other blogs, I prefer to go straight to the point and explain in a brief but enlightening way.

The goal of this post is not to become the “ultimate reference” about the topic (it is lightyears away from it) but rather, to awake some interest for its relevance and become a reference for other posts of this same blog.

Big-O and the amount of time

The above…

Glauber Cini

Software Performance Engineer wannabe

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store