はてなブックマーク

Hey, This week I wanted to discover a bit more about how dmesg works under the hood. In the past, I wanted to have alerting based on error messages popping at dmesg, so, maybe by trying to create something that uses the same thing that dmesg uses under the hood, I could better understand it. Also, I knew that in some systems, it was possible to gather the same information from kern.log and that dm

Hey, some time ago I got curious about whether gRPC would be something suitable for sending files over the wire. One of its goodness is the native support of streams, so, why wouldn’t it be? A service and a message To get the idea going, I took the approach of defining a minimum viable service, one that takes some chunks and then, once received, counts how many bytes of the actual content has been

Hey, I noticed that recently a bunch of people has been getting to the website through queries about HAProxy in the context of AWS - mainly how to receive traffic through a set of instances and forward them to another set of machines. As I aim at making this blog as much practical as I can, I feel that if I taught the basics around AWS networking first, then I could have the ground set for further

That way we can see whether Chrome would retrieve the image pushed by the / handler when we request /. I started tailoring main.go: // handleImage is the handler for serving `/image.svg`. // // It does nothing more than taking the byte array that // defines our SVG image and sending it downstream. func handleImage(w http.ResponseWriter, r *http.Request) { var err error w.Header().Set("Content-Type