Issue #102

S/W Engineering in SpaceX, Python debugging, Tail Latencies, Mental Wealth, SAGA, Distributed systems antipatterns, extract most value from tracing.

“Weekends don't count unless you spend them doing something completely pointless.”

— Bill Watterson


Posts

A simple way to get more value from tracing

This post is going to describe the tracing "infrastructure" we've built and describe some use cases where we've found it to be valuable. - #danluu

Software Engineering Within SpaceX

In addition to fueling my excitement about space travel, this launch also made me curious about the tech which goes in these rockets. I did some research from the Computer Science perspective and wanted to share what I found. - #yasoob

Ultimate Guide to Python Debugging

Lots of people resort to just using bunch of print statements to see what's happening in their code. This approach is far from ideal and there are much better ways to find out what's wrong with your code, some of which we will explore in this article. - #martinheinz

Programming is boring art

Call it engineering, or whatever you want, but I would consider programming an art. The practice of writing good code requires not just discipline but a different way of logical reasoning that leads to a different world of beauty. - #ahsmart

Getting Out of Quicksand, With DevOps!

This is a story of how you can apply the Three Ways of DevOps to get out of a state referred to as quicksand (The more you fight it, the more it pulls you in). - #pickl #blog

Why you should measure tail latencies

Even when a small fraction of requests experiences extreme latencies, it tends to affect your most profitable users, and not in a good way. - #robertovitillo

Mental Wealth

When it comes to mental health, our society approaches it like we did with physical health 50 years ago. We only think about it when something is wrong. - #jjbeshara

Anxiety in product development

I learned to recognise and work on my own anxiety. It also lead me to recognise anxiety in others. Soon I realised this does not only affect other people but also organisations and processes. - #andreschweighofer

THE HARD PART OF LEARNING A LANGUAGE

My friends tell me $LANGUAGE is better for doing $THING. After going through the online tutorial, I can see why. Maybe I’ll try $LANGUAGE for this project! Just a few things I need to figure out first . . . - #hillelwayne

Ensuring backwards compatibility in distributed systems

The move towards distributed architectures brings lots of benefits: easier testing, smaller deployable units, looser decoupling, smaller failure surfaces, to name a few. But it also brings its own set of challenges. How can a set of services evolve together in a way that doesn’t break the system? - #stackoverflow

The SAGA Pattern for Distributed Transactions in MicroServices

SAGA pattern is the most popular architectural pattern to implement transactions spanning over multiple MicroServices. It was first introduced in 1987 and is popular since then. The Saga pattern is fully asynchronous. - #nlogn


Podcast

Distributed systems antipatterns

By defining a standardized tech stack, you immediately make it harder to satisfy your teams’ diverse needs. Co-hosts Neal Ford and Mike Mason are joined by Evan Bottcher and Zhamak Dehghani to explore how to benefit from self-service options. - #thoughtworks


Video

Experience Report: Running a Distributed System Across Kubernetes Clusters - Alex Robinson