The deploy was two days old, and the metrics had been calm the whole time. The moment we turned off the cache refresh batch, ad serving stopped. A retrospective on the missing verification of what a deploy actually changed.
Manual reload, static upstreams, weak L7 observability — four limits a static reverse proxy hits in a cloud-native environment, and the four mechanisms Envoy uses to address them.
Isolation, routing, connectivity, security — VPC’s four axes pulled into one place, framed around the decisions backend engineers actually face.
Java pairs static strong typing with JVM bytecode and adaptive JIT optimization. Python combines dynamic typing with an interpreter and declarative type hints. Go ships static structural typing and a single compiler. The type-system decision drives the runtime mechanism.
CPython’s GIL serializes multithreaded execution and pushes work onto multiprocessing or asyncio. Java pinned threads 1:1 to the OS until virtual threads (Java 21) reopened the thread-per-request model. Go shipped with an M:N scheduler from day one. The model you start from decides whether your service goes thread-per-request, reactive, or multiprocess.
These three tools often sit in the same place but solve different problems. A look at how static content, dynamic content, and traffic mediation get split among them.
All three languages use a garbage collector, but the priorities differ. Java leans on generational + region GCs (G1, ZGC), Python combines reference counting with a cyclic detector, and Go runs a single concurrent tri-color mark-and-sweep. What each GC gave up is what shapes its operational profile.
Calling a function with an object is often described as pass by reference, but in memory all three languages copy values. Java copies a reference value, Python binds a new name to the same object (call by sharing), and Go copies a struct header — escape analysis decides where the values live.
Three practical topics for operating TLS on top of the basic handshake. Session resumption and 0-RTT cut the repeated cost, mTLS authenticates the client too, and ACME automates certificate issuance and renewal.
Container orchestration basics and what backend developers need to know: core objects, networking, scaling with HPA, and operational essentials.