Prometheus breadcrumbs 5
This is the last of my Prometheus breadcrumbs series where I'm gonna briefly talk about rate operators, subqueries and push gateway.
Thoughts on backend engineering, Kubernetes, cloud infrastructure, DevOps practices, and the occasional indie hacker story.
This is the last of my Prometheus breadcrumbs series where I'm gonna briefly talk about rate operators, subqueries and push gateway.
Following my Prometheus breadcrumbs series I'm gonna talk about aggregation and vector matching.
Last week we spoke about labels in Prometheus. This week I'm gonna talk about scalability, that's where all the meat is when we talk about infrastructure.
Last week I explained the types of metrics Prometheus can handle. This week I'll just speak briefly about labels.
Starting a series about Prometheus, specifically the different types of metrics you can find in Prometheus and what they are used for.
Last week I posted IPAM modes in Cilium. This week's breadcrumbs continue with Cilium and is about Load Balancing, or in other words, how Cilium can replace your MetalLB.
Last week I posted routing modes of Cilium within Kubernetes. This week's breadcrumbs are about IP Allocation modes, correct name is IP Address Management (IPAM).
Last week I posted main components of Cilium within Kubernetes. This week's breadcrumbs are about routing modes.
For the ones who don't know Cilium, it's a CNI i.e. Container Network Interface. For mere mortals this means it's the guy who handles the network stuff within Kubernetes.
Considering I'm building up a social network app, I decided to read the book The Cold Start Problem in order to learn more about social networks.
Previously we have mentioned about requests IDs to avoid mutating the backend state twice due to a network problem. But there is more about it.
One thing I've observed is that people make APIs like they are a ping-pong game. Literally they design all endpoints to respond as soon as possible.
Probably you were doing this mistake in your backend. When things go wrong and there are network connection problems, there are two possible scenarios.
Welcome to race conditions. Imagine you are about to eat a piece of cake, your fork is going closer and closer to your mouth, when suddenly, you are called and you switch your attention to somewhere else.
I was listening a podcast where one of the most influential persons in the world of AI was interviewed. What caught my attention is that it was all reduced to science or computation.
One flaw that AI has right now is the lack of full context. Not being aware of the whole context makes the AI err because it simply doesn't know better.
Even though I believe AI is going to plateau before the next real jump in the technology, I think there is still more room for AI usage before that happens.
Last few days I have been thinking into product adoption, why some products succeed while others fail and a crazy idea has just come to my head.