Blog - Konrad Kowalski (rootsher)
posts (112)
- Realtime in the Browser: From Polling to WebTransport6/7
WebTransport: Streams and Datagrams for Realtime over HTTP/3
HTTP/3 and QUIC give a single session many independent streams plus datagrams. Not all data has to arrive reliably and in order.
- Testing Through Layers: From Code to Infrastructure3/9
Integration Tests: The Real System Boundary
An integration test checks whether code works with a real dependency or a real boundary. It tests the place a unit test cannot see by definition.
Cluster Policies: Why Kyverno and CEL Exist
Cluster policies appeared because RBAC says who may create a resource, but it does not answer well whether this specific YAML is safe.
- Frontend Rendering: from server-side pages to hybrid rendering15/17
Resumability: what if we don't hydrate at all?
The server records enough information that the client never rebuilds the component tree. Code loads because execution became necessary.
Introduction to Service Mesh: Why Istio and Linkerd Exist
Service mesh appeared because, in a microservice system, traffic, identity, and observability problems started repeating in every service.
- Realtime in the Browser: From Polling to WebTransport5/7
WebSockets: A Persistent Bidirectional Communication Channel
After the handshake there are no requests and responses left, only frames. A persistent connection is state, and it reaches the load balancer, the deploy and…
- Gateway API Without the Magic4/4
Migrating from ingress-nginx to Gateway API
Migrating from ingress-nginx is not mechanical YAML translation. First, separate the application contract from controller-specific behavior.
- Testing Through Layers: From Code to Infrastructure2/9
Component Tests and Snapshot Tests: A Small Application Fragment
A component test checks a small part of the application as behavior, while a snapshot test records its output. Both sit close to the code, but they answer…
- Realtime in the Browser: From Polling to WebTransport4/7
Server-Sent Events: An Event Protocol over HTTP Streaming
A standard event format and reconnection on top of an HTTP stream. Last-Event-ID gives you resume, but it does not solve event durability in the system.
- Gateway API Without the Magic3/4
GatewayClass: A Contract With the Implementation
GatewayClass is not an environment label. It is where Kubernetes Gateway API meets a specific controller.