Cloud cost management, cancelling the move to a microservice architecture & automated self-hosted infrastructure: Twitter Highlights from the last week

Cloud cost management, cancelling the move to a microservice architecture & automated self-hosted infrastructure: Twitter Highlights from the last week

January 30, 2022

In the last7days series on this blog I’ll revisit interesting content from twitter from the last 7 days and I’ll add further comments or responses to feedback which I got. The list will have about 3-5 pieces of content to keep it crisp and I hope you like what you see!

You can subscribe to the blog also via eMail.

1) I got pwned by my cloud costs 🦍❤️ by @troyhunt

This is a forensic story, how @troyhunt found out about his exploding Azure Cloud bill and how he found out about what was causing the surge in costs.

My personal approach to cloud cost management is having my [AWS costs vsisible and as subject of alerts in Grafana]{https://johanneskonings.dev/aws/2020/11/27/aws_billing_metrics_and_grafana_cloud/}. I use the Hetzner cloud in paralle as well, which does not yet have an API-based cost reporting yet (but I’ll ask about it).

2) Why our team cancelled our move to microservices by Steven Lemon

This is a great case study about a team, which planned to switch to microservice base architecture, but then refrained from it. Most important takeaway for me was, that the main compomponent of their service was and is still a software monolith, so they would have had fancy microservices around a legacy core.

Microservices architecture planing

3) My self-hosting infrastructure, fully automated by @locmai0201

Case study about automation of self hosted infrastructure: my personal take is: kudos for having it all document so throughly.

I am on similar learning path with hosting a Django-based application on top of a Kubernetes cluster hosted by Hetzner cloud. Some personal stuff is hosted on Dokcer on my Synology box as well.

I am happy to get feedback from you!