Architecture
guest@6admin.io:~$ ls ~/tags/architecture
Do you need Kubernetes for a small team ?
A decision grid between full Kubernetes, provider-managed orchestration and an intermediate option, settled by the team's real ability to live with the stack rather than by technical fashion.
A reverse proxy in front of Perforce, or not: the pros and cons
Four ways to put TLS in front of a Perforce server and what each one costs: nginx layer-4 termination, p4d native TLS, SNI passthrough and the in-house tools P4Broker and P4P. With the client-IP trap everyone forgets.
Kubernetes, or not
Kubernetes is rarely the right first choice. An honest tour of the floors below it: podman and quadlet on one host, docker-compose, Docker Swarm, then docker or podman with Nomad and Consul and the real threshold where Kubernetes finally earns its keep.
Scale-to-zero: Sablier wakes Swarm and Kubernetes on demand
Sablier wakes a sleeping container when someone knocks at the reverse proxy, then scales it back to zero. Scale-to-zero on Docker, Swarm and Kubernetes, with the real Traefik config, the two strategies and the true price of handing it the Docker socket.
3factor: the architecture that removes state from the API
3factor is an architecture pattern, not a framework: realtime GraphQL, reliable eventing and async serverless, with one central idea, removing state management from the API layer.
Chaos engineering: breaking things for real, but not just any way
Chaos engineering is not sabotage: it is a controlled experiment, with a measured steady state, a hypothesis, real faults injected and a bounded blast radius. History, principles, tools and an honest fit for modest infrastructure.
Twelve-Factor App: the Heroku method that survived containers
Adam Wiggins's twelve factors, written for Heroku in 2011, remain the best checklist for shipping an application as a service: config in the environment, stateless processes, dev/prod parity, logs as event streams, then their translation into containers and Kubernetes.
The R.A.C.H.E method: Rapid Application Conception and Heuristic Extreme-programming
Rapid Application Conception and Heuristic Extreme-programming: the satirical method from the International Institute of La RACHE formalises what everybody already practises, with an eight-word post-it to scope the project and a FAQ that tells the truth.