Here are the concurrency best practices for predictable, reliable, and bug-free Go code. — Concurrency in Go Go is well-known and loved for its concurrency. The go runtime manages lightweight threads called goroutines. Goroutines are quick and simple to write. You just type go before the function you want to execute asynchronously, in another thread. Sounds easy enough? Goroutines are Go’s way of writing asynchronous code.

Implementing the Anti-Corruption layer by using a famous DDD pattern — Repository. — Today it is hard to imagine writing some application without accessing some storage in a runtime. Probably not even by writing deployment scripts, as they need to access configurational files that are still, in a way, types of storage. Whenever you write some application that should solve some problem in…

We continue a journey through the SOLID principles by presenting the one which has the most significant impact on code design — The Interface Segregation Principle. — Whenever someone starts with first programming lessons, the procedure is always similar: for the first couple of weeks or even months, it is all about algorithms and rewiring the brain to accept that way of thinking. At some point, we start with an introduction to Object-Oriented Programming. If teachers wait…

We continue a journey through the SOLID principles by presenting the one which has the most significant impact on unit testing in Go — The Dependency InversionPrinciple. — Learning a new programming language is often a straightforward process. I often hear: “The first programming language you learn in a year. The second one in a month. Third one in a week, and then each next one in a day.”. Saying that is an exaggeration, but it is not…

We start a journey through the essential principles in software development by presenting the most known one — The Single Responsibility Principle. — There are not too many possibilities for a breakthrough in software development. They mostly come as rewiring the logic after wrong initial learning or filling up a missing piece in our knowledge. I like that feeling of more profound realization. Sometimes during a coding session, sometimes while reading a book…

We continue a journey through the SOLID principles by presenting the one which has the most complicated definition — The Liskov Substitution Principle. — I am not a reading-type of person. Too often, when I read, I realize that I do not follow the topic of a text for the last few minutes. Many times I go through the whole chapter without knowing what it was about in the end. Sometimes it is frustrating…

We continue a journey through the SOLID principles by presenting the one which gives flexibility to applications — The Open/Closed Principle. — Many different approaches and principles provide a long-term improvement in our code. Some of them are well-known in software development society, and some are somehow under the radar. My opinion is that is the case with The Open/Closed Principle, which stands for the letter O in the word SOLID. …

Code patterns to make your programs more reliable, efficient, and make your life easier — I’ve been developing EDR solutions for 7 years. That means I have to write long-running system software that’s both resilient and efficient. I heavily use Go for this job, and I’d like to share some of the most important code patterns that you can count on to make your program…

Harnessing one of the most useful packages in go — Applications in golang use Contexts for controlling and managing very important aspects of reliable applications, such as cancellation and data sharing in concurrent programming. This may sound trivial but in reality, it’s not that so. The entry point for the contexts in golang is the context package. It is extremely…