Posts in category "software-development"

What is it? It started as an exercise that was supposed to satisfy few, artificial requirements for a technical interview. I have never attended the interview but most of the solution was ready and I thought I will keep going to learn new and solidify existing knowledge. It incorporates few techniques and technologies …

Appendices A. Concept of volumeMeter All scenarios are using a mysterious variable volumeMeter. It allows me to emulate lag of volume measurement in controlled fashion Note: You don't need to study the contents of volumeMeter as long as you assume that it is a function that provides current volume and is designed to …

Asynchronous approach (ctd) Channels (ctd) Solution with channels and a Goroutine This solution uses Goroutine to measure volume upon request, and a request and response channels to communicate between Goroutine and main loop. In practise, the volume measurement is continuous, because request for volume is sent as soon …

Asynchronous approach (ctd) Channels (ctd) Channel and Goroutine None of the previous examples demonstrated channels in the environment where they make most sense - concurrent one. My intention was to keep the examples as simple as possible and, at the same time, demonstrate the use of channels in synchronous way. What …

Asynchronous approach (ctd) Channels (ctd) Select statement If you want to embrace Go's channels, but are feeling constrained by all the blocking operations on them, select will make your day. It is part of Go's syntax and - in its simplicity - it's stunning how powerful it is. Link to documentation. Non-blocking …

Asynchronous approach (ctd) Channels Channels are extremely important in Go. They require shift of concurrent system design paradigm but they also ease you into it. I'm not going to scrimp on space to introduce them. What are channels in Go? Channels are the pipes that connect concurrent goroutines. You can send values …

Asynchronous approach (ctd) Mutex Term stands for mutual exclusion. In programming it is a property limiting resource access to one thread (or even one consumer - due to lack of reentrancy, later about that) at a time. Sounds familiar? In previous section the atomic functions were helping us achieve just that in …