https://www.komu.engineer/ Komu Wairagu 2025-04-25T00:00:00.000Z https://www.komu.engineer/blogs/12/propagate-context-without-cancellation.html 2023-08-23T00:00:00.000Z

Sometimes you need to propagate a context's values without also propagating its cancellation. In what situations would you run into such a need? How do you do that? What solutions exists in the ecosystem? Is this something that Go itself should solve? Let's find out together in this post.

https://www.komu.engineer/blogs/11/opentelemetry-and-go.html 2023-02-17T00:00:00.000Z

This guide should take you from zero to production in instrumenting, collecting, and exporting telemetry data(metrics, logs, and traces) in a secure and scalable manner.

https://www.komu.engineer/blogs/10/dont-use-a-different-interface-for-testing.html 2022-05-22T00:00:00.000Z

Your test code should not be using a different interface implementation compared to your non test code. Using different implementations(sometimes called 'mocking') is one of the best ways to lie to yourself that you are testing your code whereas you really aren't. This article articulates why, including code examples.

https://www.komu.engineer/blogs/09/log-without-losing-context.html 2020-05-26T00:00:00.000Z

In order to minimize logging costs, conventional wisdom asks that you filter logs by severity and/or implement sampling. This article articulates why that may be a bad idea, it then proposes an alternative that loses you neither money nor context and then finally it presents a proto-type implementation of that alternative.

https://www.komu.engineer/blogs/08/golang-stackTrace.html 2019-11-18T00:00:00.000Z

This article assumes that you have come to the conclusion that you need stacktraces in your errors. We are going to build a package that can annotate any errors - including the ones created by the stdlib errors package - with stack traces.

https://www.komu.engineer/blogs/07/understand-how-celery-works.html 2019-07-15T00:00:00.000Z

How do Celery, Resque, Sidekiq, among other background task processors work? In this blogpost, we figure that out while building our own background task processor one step at a time.

https://www.komu.engineer/blogs/06/timescaleDB-for-logs.html 2018-11-23T00:00:00.000Z

It's almost unheard of, these days, to store application logs in a structured datastore. In this blogpost I propose and implement a logging pipeline that involves storing logs in PostgreSQL(timescaleDB)

https://www.komu.engineer/blogs/05/lambda-shim.html 2018-10-01T00:00:00.000Z

Sometimes you may have a usecase for AWS lambda but the programming language that you are using is not natively supported by AWS lambda. But you can still use your favorite programming language with AWS lambda even if it is not natively supported. In this article, we explore how to do that.

https://www.komu.engineer/blogs/04/go-modules-early-peek.html 2018-07-20T00:00:00.000Z

In this article, we add versioning to a go package while working outside of GOPATH. We take a peek into the future of developing in Go, we stumble and we rise.

https://www.komu.engineer/blogs/03/python-lambda.html 2018-06-02T00:00:00.000Z

In this article, we will go through an example of how to migrate a python application to AWS lambda. We will not make any code changes(or re-architect it) to our app in order to migrate it.

https://www.komu.engineer/blogs/02/consensus.html 2018-03-24T00:00:00.000Z

How do you get different computers that are part of a larger cluster to agree on what the value of something is? We try and answer that question. We also learn about, CASPaxos, the consensus protocol.

https://www.komu.engineer/blogs/01/go-gc-maps.html 2018-01-25T00:00:00.000Z

I'm left wondering, shouldn't the Go runtime then not do it for me/you by default? Anytime the runtime sees a map that is larger than X and the keys to that map contains pointers, the runtime inlines(for lack of a better term) that map into one whose keys are ints(or whatever) and does the string->ints hashing for you without you even noticing.