Today I was trying out the latest version of nginx. I was trying to build it from scratch on my MacOS machine, and it seemed pretty straight forward to build and use :D Let’s see what I did Note: I assume that you have development tools like make installed. I installed them by doing xcode-select --install For detailed docs on configuration for compilation, check https://nginx.org/en/docs/configure.html The latest version of nginx as of this writing is 1.

In this post, I wanna jot down my thoughts on rate limiting while I ponder about it and learn more about it and understand the why, what, how So, what’s rate limiting? Before going there to answer that question, let’s see a scenario that can happen in the realy world Let’s say you build a service. It’s a long running service that responds to network requests, for example HTTP requests to an HTTP API served by your service

Recently I was checking out Kong’s Open Source Kong API Gateway and Kong’s documentation on services and routes when I stumbled upon Mockbin, an interesting service by Kong, and it’s open source! mockbin source code is here - https://github.com/Kong/mockbin . According to their website, in short what Mockbin does is - Mockbin allows you to generate custom endpoints to test, mock, and track HTTP requests & responses between libraries, sockets and APIs.

Recently the PostgreSQL community released PostgreSQL v15, which is the latest version as of this writing. I thought I could try out and experiment with the latest and greatest of PostgreSQL so I got my hands on this version with some basic steps # Get prebuilt binary links from a trusted source. For example https://www.enterprisedb.com/download-postgresql-binaries wget https://sbp.enterprisedb.com/getfile.jsp?fileid=1258215 -O pg-15-osx-binaries.zip unzip pg-15-osx-binaries.zip sudo xattr -r -d com.apple.quarantine pgsql ./pgsql/bin/postgres --version ./pgsql/bin/psql --version .

A colleague, Madhav Jivrajani, recently posted about the debug/buildinfo standard library package in Golang in my company slack channel https://pkg.go.dev/debug/buildinfo It is a package present from golang 1.18beta1 version So I figured I’ll give it a try than defer it for later ;) I got the beta version using gvm gvm list-all -u gvm install 1.18beta1 gvm set 1.18beta1 go version Then I used VS Code editor to start off a small demo project to try out the debug/buildinfo package.

I think this is very intuitive and straight forward topic. Pretty cliche too. But I think it’s important to talk about it nevertheless There are so many technical articles on the Internet. Lot of technical content. Many of them also include code. I have seen different websites display code in many different ways. In my blog, the code display is very very basic actually 🙈 But I have high expectations from other people now 🙈 Let’s go over them!

I love the current era of software for some reasons. It’s making lives easier at times. For example - there’s tons of tooling out there to help with a lot of things People writing new products and software and tech are also considering things like upgradability, maintenance, migration etc For example, if you are migrating a software from one major version (semantic versioning) to another major version, and also doing cool crazy stuff like doing skip upgrades like v3.

I haven’t reviewed so many Pull Requests (PRs) to be writing about them. But reading some of the reviews for my PRs and also others PRs and also having done a handful, I have come to realize a few simple things for reviewing PRs. So let’s get right into and see what they are! :) First off, I want to call out that every tip / advice / “best practice” / idea is based on a particular context.

Recently I have been trying to learn things on my own - as in, not following the formal education path - which is to pay for a online course and attend it But in the journey I noticed quite some free online structured courses and also other ways to learn things, all for free. Paying for learning something is something I consider a bit overrated, but yeah, I do agree that there are quite some good paid content online and offline - paid online courses, paid offline courses, paid online and offline books etc

In this time machine series blog post, I’m going to go back in time and recall an interesting problem we faced. We faced many interesting problems actually. I’ll try to cover each one of them in a time machine series blog post :D For now I’m just noting down all the bits and pieces in my notes based on whatever I can recall! Now, let’s checkout what problem we faced with respect to database connections!