Weekly Digest #76

Articles

My Twitter journey from 100 -> 30k followers

• 100 → 200: extremely difficult, demotivating, and I had no idea what I was doing.
• 200 → 1,000: committed to build an audience seriously on Twitter. I bought a Twitter course, learn the basics, get to know the “algorithm”, tried everything.
• 1,000 → 6,000: stay consistent, leverage my advantage, build in public, get lucky.
• 6,000 → 10,000: still stay consistent, build in public, share my journey, threads, memes, giveaways, advice, etc.
• 10,000 and above: did all of the above, but with less time as things are easier now.

Borg, Omega, and Kubernetes

Lessons learned from three container-management systems over a decade

• Borg, was built to manage both long-running services and batch jobs, which had previously been handled by two separate systems: Babysitter and the Global Work Queue.
• Omega,an offspring of Borg, was driven by a desire to improve the software engineering of the Borg ecosystem. It applied many of the patterns that had proved successful in Borg, but was built from the ground up to have a more consistent, principled architecture.
• Kubernetes.It was conceived of and developed in a world where external developers were becoming interested in Linux containers. Like Omega, Kubernetes has at its core a shared persistent store, with components watching for changes to relevant objects. In contrast to Omega, which exposes the store directly to trusted control-plane components, state in Kubernetes is accessed exclusively through a domain-specific REST API that applies higher-level versioning, validation, semantics, and policy, in support of a more diverse array of clients.

Things to avoid:

• Don’t Make the Container System Manage Port Numbers
• Don’t Just Number Containers: Give Them Labels
• Be Careful with Ownership
• Don’t Expose Raw State

Machine learning at Wolt: our journey towards MLOps