Analytics V3

Lately, I've been working with Go more and thought that it would be worth revisiting the suite of microservices I built using Deno last year, including my Notion-integrated analytics and redirect services. Version 3 of analytics is the Go rewrite of the Deno version (v1 and v2), bringing down the system resources needed to run each service from about 30MB of RAM to just 2-5MB per service. Docker image sizes are also down to just under 20MB compared to much more for the Deno version.

The new V3 service is also compatible with existing V1 and V2 endpoints - so it is possible to call /v1/campaign/:id or any V2 endpoint as before. But, the new V3 endpoints have some additional consistency updates as well as an improved GET feature for building custom dashboards if desired - so I'd recommend using the new endpoints if possible.

Lower System Resources = Lower Costs

This update is particularly important for my use case where I don't want to spend a huge amount of money on cloud hosting for personal projects - so I have a particularly tiny VPS with only 512MB of RAM. With the neglible addition of running both new Go-based analytics and redirect services (10MB) along with my portfolio (about 30MB) and mura, my custom scheduling service + API also written in Go, (about 30MB), I'm only using about 70MB of RAM total. This is a huge improvement over the previous 120MB+ of RAM I was using with the Deno version of analytics and redirect services and means I could run even more additional microservices/etc in the future without needing to upgrade my server.

New Features

If you'd like to learn more about the new features and such, I'd recommend you click over to the project page or GitHub repo (linked as a related item here) and read more about it. I'm really pleased with the documentation I've written for this project, and it is one of the most comprehensive I've written (although if you find ways to improve it, feel free to PR the GitHub repository!).