Go

In order to process a lot of work we have to parallelize work across all cores, and especially if it’s CPU bound. Go has goroutines, which can be used to parallelize the work, but there is the cost of context switching for a lot of goroutines. Minimizing this context switching can be achieved by using a fork-join model when processing work. Parwork solves this problem by using goroutines, channels and waitgroups. It creates workers (goroutines) that pull work of a queue (channel), process the work and report the work back to a queue (channel). This is done in a abstracted way so the user has to provide implementation for: ...

This is probably one of the most useful “cloud” patterns out there and it is fairly easy to implement. There are great articles and implementations, like Polly, already on the internet about this pattern so why another one? Κρείττον οψιμαθή είναι ή αμαθή. Socrates 469-399 BC., Philosopher Which translates to: Better too have learned lately than never, as he tried to explain why he learned to play guitar in his old age. ...

Event sourcing is capturing all changes of an application state as a sequence of events. Since we only store events we only have to add events to a store, in contrast to updates for keeping the application state. A much simpler model that scales very well. When needing the application state we just aggregate the events into More on this can be read all over the internet but two excellent links are available below: ...

Almost every application logs data one way or another. There are a plethora of logging packages available for golang. There is the one that comes with the standard packages which takes a simple approach. There are many logging packages that follow the well established leveled approach, and there are really a lot of them. The decision of choosing a specific library comes with the cost of a direct dependency. But why should we depend directly on a specific package? How painful is it to exchange a logging package for another when we already created a lot of code with a direct dependency? This is the reason why apaptlog came to life. ...