The Stability Mindset

The Stability Mindset
I have background on software development. Currently, I'm leading a team of highly effective engineering's where we are responsible of some of the components we delivery in production and I need to say that is not the standard reality on it market. Development is used to break things and move faster, however, lots of developers never cared about production or about “polishing” they systems. This effect happens some several reasons like:
  • Having different people to develop and operate software
  • Having different departments for development and Operations
  • Having development teams focus too much in new features rather than real UX
So there is this culture clash when we have developers doing DevOps Engineering(I say that for my own experience). We developers are not used to keep something running no matter what. To be always available and reliable. It takes some time to get this “Stability Mindset” but once you get it is hard to get out of your veins.



What is stability?
IMHO Stability is not about freezing things. So you need to engineer new features but you need to make sure you don't disrupt your service. How do you make sure you don't add disruptions? There are several practices for instance:
  • Testing, Testing, Testing
  • Telemetry and Alerts Automation
  • System internals Observability(error observability, app metrics, health checkers, distributed tracking, etc…)
  • Roll Out strategy: Change one client per time, step-by-step.
  • Have a fallback or rollback strategy is something goes wrong.
  • Coding for Stability Mindset
Coding Stability Mindset
Some time ago lots of folks down here in brazil was talking about “Defensive Programing” and i really think is something similar but for Stability. So for instance I work a lot with cloud and for instance lots of things I do run in background so If I do have proper Observability - easily could have lots of things going wrong and we will know on the worst way possible. What I mean by proper Observability, I mean basic things, like for everything you engineer you add:
  • OS automation(like ansible + Jenkins)
  • Notifications(I like to create Slack channels that ping me if something goes wrong)
  • Log everything(don't forget add logrotate)
  • Look Dashboards everyday(It help to build mental patterns and know you workloads in sense of “feeling” so you might smell is something is not ok.)
  • When you call any API have: Retries, Fallbacks, Timeouts.
  • Expose System/App metrics so you can understand what's happening internally
Is you release some shared component or service without this thing you can have proper debuggability/observability so you might not be proactive enough to leverage your user's experiences.  Another key thing in order to improve users experiences(developers) is great documentation and also abstractions. Don't expose all parameters, hide things and have good default this make adoption of thing easier. This concerns can be added later however they often take lots of time. I don't think a component/service can be released without this items I don't feel comfortable at least.

Being Lean on Binaries
It's usual to have components that are integrated into microservices code in this cases you need make sure to be as much lean as possible. Add only what is strictly necessary it might be better to “copy” some code and adding frameworks? Why? Because you can create some JAR HELL easily with your consumers.

That's something very unusual for developers. We often are familiar with re-use however in this scenarios re-use can be very tricky and might not pay off in a long run. How never had issues with Guava? AWS SDK?  This could be considered another item of the “Coding for Stability” since you might avoid problems for your end users by having this concerns before building anything.

Productivity as end Goal
In the end of the day, we want make developers more productive. We don't want to make developers more “restrict” or be heavily “Opinionated” of some solutions. There is high need for developer teams independence, however, is we don't have Stability mindset running in our veins we might provide poor user experience and end up with something that's a problem and slow down developers rather than speed up productivity.  Stability Mindset is something very hard to get from the beginning but as you practice you can get it and deliver better solutions.

Cheers,

Diego Pacheco

Popular posts from this blog

C Unit Testing with Check

Image
When I start on IT, several years ago(+15), C was the first language that I learned. But was not the first language I mastered and deployed in production which was...surprisingly Visual Basic 6.0. However, when I learned C or any language back on that old and arcane time noddy was into testing. However now is impossible to work professionally in any language without tests. C is a low-level language but still kicks ass and has several interesting libs/frameworks. People use to fear C a lot because of lack of syntactical sugar but once you get used to it is not that hard at all. Today I want to show how you can do Unit Testing with C. I will not show how to do Unit Testing with C++ but with C ANSI actually. We will be using Check a unit test lib for C ANSI.
read more »

Having fun with Zig Language

Image
Zig is a general-purpose language created in 2016 by Andrew Kelly .  Zig aims to fix the issues C language has while being pragmatic and simple at the same time. Zig really shines as being simple by not having any hidden control flows, not having hidden memory allocations, no pre-processors, and no macros. Basically, it's one language and one language only. Since pre-processors and macros can get really complex and become their own universe. Sure it's not the Zig Philosophy.  Zig Compiler(Zig cc) also is a C compiler, and the interoperability from C to Zig is very good. Clearly, we can see influence from other languages like Go and Rust; however, Zig is pretty unique and different from Go and Rust.  Zig is fast. Zig is perfect for system programming. I bet we will see a lot of solutions being built in Zig. As a languages aficionado, I like to learn at least one language per year and sometimes more; Zig was my 2021 pick, did not regret it. Even if you dont use all language...
Keep reading

HMAC in Java

Image
In 2018 AWS CTO(Vogels) said : "Security is everyone's job". For the last 2 years, there was so many famous and big data leaks and breaks that made that statement be very true more than ever. Security often could mean worst performance and worst user experience so in order to get it right you really need to think about the designs before jumping into to code and consider performance and user experience has main requirements.  I was thinking about writing about how to do HMAC in Java for a while and recently Redis 6.0.0 come out and to my surprise, there was a refactoring on the password part in order to use HMAC.  Security easily could scare engineers often because it is not something well spread yet but I believe this will change soon. It does not matter if you have to deal with PII Data or not, security is super relevant because everybody is running their workloads at the cloud or with IoT and Edge devices which means more distribution, more code, more points of fail...
read more »