The is no perfekt database. But there is a best database for each use case (or even a combination of). SQL is still sometimes the best choice. Compare to cars: The Mercedes G-Wagon is perfect for off-road, but bad on a race track. The opposite is true for a Porsche GT-3. Both are cars.
I upgraded my Kubernetes cluster from 1.33.1 to 1.33.5.
Upgrade succeeded.
Control plane healthy.
Nodes ready.
Then production broke.
A critical plugin my application depends on is not available for 1.33.5 yet.
What would you do to fix this incident?
#Kubernetes#DevOps#SRE
Observability allows you fully understand every click in the UI and all events that follow, all involved services, all databases, all session specific parameters and the timing everything including the specific location of errors and performance issues. Monitoring is just a subset of this.
@kmichaelc@0xlelouch_ The mux knows my routes and my handlers. They are calling my business logic. Very thin layer, not much to code and not much of boilerplate.
@dkrizic@0xlelouch_ Well I don't think it's a price anyone should consider paying lightly. Usually by generating boilerplate, you end up with a worse version of the 'framework' you're trying to avoid
Use a framework if you want to. Use net/http of you really really know what you're doing
If you are building a backend in Golang today, which stack would you choose?
1. Gin
2. Echo
3. Fiber
4. Chi
5. gRPC
6. net/http + custom middleware
Curious what people are picking now cause Go backend has become very interesting.
Wir müssen keine Angst haben! Künstliche Intelligenz ist nur wie ein Papagei, der die Wahrscheinlichkeit für das nächste Wort berechnet. Hört auf Deutschlands KI-Expert:innen.
@brankopetric00 I would first ensure that the endpoints of the service shows all the pods. In the Ingress or HTTPRoute I would ensure that the service is configured correctly
You have 3 replicas of a service. Kubernetes says all 3 are Running and Ready.
But your users report that roughly 1 out of 3 requests fails with a 502.
- Readiness probes pass on all pods
- Liveness probes pass on all pods
- The failing pod responds to curl from inside the pod
- Logs on the failing pod show no errors
Something is lying to you. What is it?