DEV Community: Krzysztof Góralski

Weekly Links #19

Krzysztof Góralski — Sun, 29 Dec 2019 17:44:07 +0000

Software architecture trends 2020 by infoq
Readable Code by Gergely Orosz
Distributed systems learnings in 2019 by Gergely Orosz
Production Checklist for web apps on Kubernetes by https://srcco.de/
Service Delivery Review: The Missing DevOps Feedback Loop? by Matthew Philip
Beyond Microservices: Streams, State and Scalability by Gwen Shapira
The Architecture of a Large-Scale Web Search Engine, circa 2019 by https://cliqz.com/
Spring Transaction Management: @Transactional In-Depth by Marco Behler
JVM Garbage Collectors Benchmarks Report 19.12 by Ionuț Baloșin
Java Microservices: A Practical Guide by Marco Behler
Goto and the folly of dogma by Gustavo Duarte
I sat in on a Honeycomb incident review and you won't believe what we learned next by Jacob Scott
On the first use of the term "Programming Language" by http://www.cs.uni.edu/
Linux kernel preemption and the latency-throughput tradeoff by Matt Fleming
The Kernel Change That May Be Slowing Down Your App by Karl Matthias
Debezium 1.0 Final Is Out by Gunnar Morling
GCP: Availability, scale, and ease of management with new Layer-4 Internal Load Balancing features by Babi Seal
How to write a Cluster API provider for running Kubernetes cluster on baremetal by Himani Agrawal
Performance Resources by Matt Fleming
Fixing Management by Matt Heusser
Resilience Roundup - When mental models go wrong. Co-occurrences in dynamic, critical systems - Issue #61 by Resilience Roundup
A conjecture on why reliable systems fail by Lorin Hochstein
Why incidents can’t be monocausal by Lorin Hochstein
Making Kotlin Ready for Data Science by Andrey Cheptsov
Demonstration of various hardware effects by Jakub Beránek
30secondsofinterviews.org
chaoskube periodically kills random pods in your Kubernetes cluster. by Martin Linkhorst

Weekly Links #17 #18

Krzysztof Góralski — Sun, 15 Dec 2019 09:33:18 +0000

Modular Monolith: A Primer by Kamil Grzybek
The power of relationships in data by Werner Vogels
The Hardest Part About Microservices: Your Data by Christian Posta (old article, but brilliant)
Microservices and the Inverse Conway Manoeuvre by James Lewis
Building a High-Performance Networking Protocol for Microservices by Robert Roese, Arsalan Farooq
Microservices instrumentation by JBD
Primer: Understanding Software and System Architecture by Catherine Paganini
Primer: Understanding the Cloud Native Impact on Architecture by Catherine Paganini
How DevOps Has Impacted Development – A Look at the Before and After by Georgi Todorov
The company isn’t a family by DHH (David Heinemeier Hansson)
Board: 60+ companies represented. 150+ ppl Experiments that resulted in increased momentum Experiments that "failed" from john Cutler
You build it, You run it (Why developers should also be on call) by Chris O'Dell
Web Developer Security Checklist V2 by sensedeep.com
Software Testing Guide by Martin Fowler
100 Best DevOps Stories of 2019— Faun by Aymen El Amri
Uncovering Hidden Business Rules with DDD Aggregates by Nick Tune
A Sociotechnical Toolkit by Nick Tune
An example of an Architecture Guild repository by Jakub Nabrdalik
Deliberate side-products by Gojko Adzic
Log Management by John Vester
The Amazon Builders' Library by AWS
Takeaways from AWS re:Invent 2019’s Amazon DynamoDB Deep Dive: Advanced Design Patterns by Jeremy Daly
Awesome DynamoDB by Alex DeBrie
Shave 99.93% off your Lambda bill with this one weird trick by Michael Hart
Serverless - Lessons learned by Paul D'Ambra
AWS re:Invent 2019: How Verizon Media implemented push notification using Amazon DynamoDB by Jon Mccamant, Suneel Joshi, Bob Leano, Harshil Shukla
AWS re:Invent 2019: Firecracker open-source innovation by Radu Weiss, Alexandra Iordache, Sebastian Bernheim
Amazon EKS on AWS Fargate Now Generally Available by by Martin Beeby
Correctness proofs of distributed systems with Isabelle | Code Mesh LDN 19 by Martin Kleppmann
Hazelcast Resilient to Kubernetes Zone Failures by Rafal Leszko
Awesome Command-Line Tools by vimfromscratch.com
WireGuard VPN is a step closer to mainstream adoption by Jim Salter
They Might Never Tell You It’s Broken by Maxime Chevalier-Boisvert
Benchmark Surprises by Gopher Academy
Parsing 18 billion JSON lines with Go by Roffe
Sneaky race conditions and granular locks by Roberto Clapis
Go advanced concurrency patterns: part 3 by Roberto Clapis
Dynamically scoped variables in Go by Dave Cheney
Hubble - Network, Service & Security Observability for Kubernetes by cilium
Circuit Breaking in Spring Cloud Gateway with Resilience4j by Piotr Mińkowski
Continuous integration and deployment with Bazel by Benjamin Peterson (Dropbox)
BPF: A New Type of Software by Brendan Gregg
My learnings on Linux BPF container performance engineering by Marcel Dempers
Java JDK 14 by OpenJDK
OpenJDK: State of Valhalla by Brian Goetz
What to Expect in Kotlin 1.4 and Beyond by Svetlana Isakova
R2DBC goes GA by by Mark Paluch
How to identify a strong sysadmin job applicant by Joachim Haller
Oxide Computer Company: Initial boot sequence by Steve Tuck, Bryan Cantrill and Jessie Frazelle
Free Book: A Comprehensive Guide to Machine Learning (Berkeley University) Posted by Capri Granville
The Lesson to Unlearn by Paul Graham

Weekly Links #15 #16

Krzysztof Góralski — Sun, 01 Dec 2019 18:56:54 +0000

Common mistakes when moving to microservices by Jakub Nabrdalik
Extended BPF: A new software type by Brendan Gregg
Kubernetes’ Is the Future of Computing. What You Should Know About the New Trend. by Tae Kim
Addressing by Marek Majkowski
API Gateway: Dream vs Reality bhy Bob Roel
Creating a Production Launch Plan by Alec Warner & Vitaliy Shipitsyn with Carmela Quinito
Availability and Region Failure: Joint Consensus in CockroachDB by Tobias Grieger
Logging patterns and their performance impact by Ionut Balosin
Configuring container networking with Podman by Brent Baude (Red Hat)
BPF Performance Tools (book) by Brendan Gregg
[Mergeable replicated data types – Part I]](https://blog.acolyer.org/2019/11/25/mergeable-replicated-data-types-part-i/) by Adrian Colyer
Mergeable replicated data types – Part II by Adrian Colyer
Local-first software: you own your data, in spite of the cloud by by Adrian Colyer
RSocket Messaging with Spring by Rossen Stoyanchev
QCon London 2019: Mature microservices and how to operate them by Sarah Wells
The First Non-Bullshit Book About Culture I’ve Read by Ian Miell
An Engineering Team where Everyone is a Leader by Gergely Orosz
Kafka, GDPR and Event Sourcing by Daniel Lebrero
The epistemology of software quality by Hillel Wayne
A guide to distributed teams by Juan Pablo Buritica and Katie Womersle
Reactive planning and reconciliation in Go by Gianluca Arbezzano
OpenJDK Startup - Late 2019 Edition by Claes Redestad
Introducing ksqlDB by Jay Kreps
The Architect of Modern Algorithms by Susan D'Agostino
Designing Services That Deliver by G. Lynn Shostack
The Efficiency-Destroying Magic of Tidying Up by Florent Crivello
Composition over inheritance applied to Docker by Nicolas Fränkel
Decoupling, Architecture and Teams by Mike Hadlow
Production Readiness Checklist by gruntwork
The Kubernetes Learning Resources List
KubeCon + CloudNativeCon North America 2019
EnvoyCon 2019 San Diego
Thoughtworks Technology Radar 21

Weekly Links #14

Krzysztof Góralski — Sun, 17 Nov 2019 10:48:43 +0000

The Service Mesh: What Every Software Engineer Needs to Know about the World's Most Over-Hyped Technology by William Morgan
Decisions, Decisions or Why Baskets of Options Dominate by Kent Beck
Video: Linux Systems Performance by Brendan Gregg, Netflix
Kotlin Not-to-Do List - What we should avoid doing in Kotlin by Marcin Moskała
Effectively Sealed Classes in Java by Grzegorz Piwowarek
The Value in Go's Simplicity by Benjamin Congdon
Good Go: Contributing to encoding/json by Phil Pearl
Google’s new chip design protects the cloud where it’s most vulnerable by Patrick Howell O'Neill
The definitive guide to make software fail on ARM64 by Ignat Korchagin
Algorithmic Nuggets in Content Delivery by Bruce M. Maggs, Ramesh K. Sitaraman
Snap: a microkernel approach to host networking by Adrian Colyer
Announcing the Bytecode Alliance: Building a secure by default, composable future for WebAssembly
Helm 3.0.0 has been released! by Helm Blog
The API Gateway security risk you need to pay attention to by Yan Cui
CockroachDB Passes TPC-C at 100k Warehouses by by Andy Woods, Jesse Seldess and Andrew Werner
Stack Overflow Considered Harmful? The Impact of Copy & Paste on Android Application Security by Felix Fischer
Kubernetes, Pod Security Policies: Seccomp
Amazon SNS Adds Support for Dead-Letter Queues (DLQ)
Amazon DynamoDB adaptive capacity now handles imbalanced workloads better by isolating frequently accessed items automatically

Weekly Links #12 #13

Krzysztof Góralski — Sun, 10 Nov 2019 18:20:10 +0000

EventStorming Modelling Tips to Facilitate Microservice Design by Sophie Mansfield
Book Review: Introducing EventStorming by Nick Tune
How many metrics should an application return? by Brian Brazil
The Consul outage that never happened by Devin Sylva
Future Ready Enterprise Systems by Bhaskar Ghosh, Adam Burden, James Wilson
Hot SRE trends in 2019 (brought to you from SREcon EMEA) by Will Sewell
Scaling in the presence of errors—don’t ignore them by programming is terrible
LISA2019 Linux Systems Performance by Brendan Gregg
KPTI/KAISER Meltdown Initial Performance Regressions by Brendan Gregg
Linux Load Averages: Solving the Mystery by by Brendan Gregg
SYN packet handling in the wild by Marek Majkowski
Creating sockets by Marek Majkowski
Fastly Expands Serverless Capabilities With the Launch of Compute@Edge by Fastly Blog
How Many Go Developers Are There? by Russ Cox
Go Modules: v2 and Beyond by Jean de Klerk and Tyler Bui-Palsulich
E-Book: Kubernetes Patterns - Free Download
Kubernetes made my latency 10x higher by Galo Navarro
Thank you, Guido by Dropbox Team
Join Ordering Part II: The ‘SQL’ by Justin Jaffray
Parse, don’t validate by Alexis King
Comparing Ingress controllers for Kubernetes by Flant Stuff
Building and deploying lots of microservices using werf and GitLab CI by Flant Stuff
OpenTitan - open sourcing transparent, trustworthy, and secure silicon by Royal Hansen
GraphQL Search Indexing by Netflix Technology Blog
Working at Silicon Valley Companies - in Europe by Gergely Orosz
What Every Programmer Should Know About Floating-Point Arithmetic by floating-point-gui.de
Helm v3.0.0-rc.1

Weekly Links #10 #11

Krzysztof Góralski — Sun, 27 Oct 2019 08:06:20 +0000

Sense and Nonsense in Event Thinking and Microservices by Jan Stenberg
Hello, production - On the value of getting a functional, but useless version of a new application into production as soon as possible. - by Pete Hodgson
SLOs Are the API for Your Engineering Team by Charity Majors
How LinkedIn customizes Apache Kafka for 7 trillion messages per day by Jon Lee and Wesley Wu
How Multiplexing Changes Your HTTP APIs by Mark Nottingham
HTTP/2 (SPDY)and HTTP/3 (QUIC) by Anshu Mishra
Yes, You Should Estimate Software Projects by Gergely Orosz
Normality is a myth by Andrey Akinshin
Test Desiderata by Kent Beck
Kubernetes: Operators and Controllers, What is the Difference? by Josh Rosso
Security in the Age of Docker & Kubernetes by David Dooling
CPDoS: Cache Poisoned Denial of Service by Hoai Viet Nguyen and Luigi Lo Iacono
Request smuggling between Amazon ALBs and Go net/http by Adam Scarr
Persistent Disks and Replication by Jaana B. Dogan
Simplifying web deploys by Pinterest Engineering
Is GraphQL Still Relevant in an HTTP2 World? by Marc-André Giroux
Principled GraphQL by Geoff Schmidt and Matt DeBergalis
Spring Creator: What Went Wrong with Enterprise Java by Rod Johnson
Don't Put Fat Jars in Docker Images by Philipp Hauer
Memory Footprint of a Java Process by Andrei Pangin
Understanding low latency jvm gcs V2 by Jean-Philippe Bempel
What’s new in Spring Boot 2.2? by Tim van Baarsen
The 2019 Java Developer RoadMap
Uber Golang Style Guide

Weekly Links #9

Krzysztof Góralski — Thu, 10 Oct 2019 19:51:52 +0000

AWS billing is broken and Kubernetes won't last by Corey Quinn
What we know We don't know by Hillel Wayne
On Hating Your Tools by Hillel Wayne
Enterprise Software Is Dead: Going forward it’s all just business software. by Austin Petersmith
Microservice Observability, Part 1: Disambiguating Observability and Monitoring by Tyler Treat
USETL: Unikernels for Serverless Extract Transform and Load Why should you settle for less? by Henrique Fingler, Amogh Akshintala, Christopher J. Rossbach
Why I Recommend My Clients NOT Use KSQL and Kafka Streams by Jesse Anderson
High-level view of the Open Source Firmware Ecosystem in Communications of the ACM by Jesse Frazelle
Applying deep learning to Airbnb search by Adrian Colyer
GOTO 2019 • Principles for Developing More Secure Systems by Eleanor Saitta
Push configuration with zero downtime using Cloud Pub/Sub and Spring Framework by Elena Felder
Performance Matters by Emery Berger
The benefits and Challenges of Bringing Infrastructure as Code into a CD Pipeline: Honeycomb Q&A by Rupert Field
Terraform at Starbucks: Infrastructure as Code for Software Engineers by Mike Gee, Ryan Hild
Managing Global CDN Operations at Netflix by Hrishikesh Barua
When TCP sockets refuse to die by Marek Majkowski
"The three pillars of observability" thread by Ben Sigelman
Event Modeling: What is it? by https://eventmodeling.org
The Top 10 Most Common Mistakes I’ve Seen in Go Projects by Teiva Harsanyi
Use internal packages to reduce your public API surface by Dave Cheney
Proposed to target JDK 14: JEP 349: JFR Event Streaming by Erik Gahlin, Markus Grönlund
JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector by Thomas Schatzl

Weekly Links #8

Krzysztof Góralski — Thu, 03 Oct 2019 20:39:35 +0000

On Eliminating Error in Distributed Software Systems by Colin Breck
Observations on Observability by Colin Breck
Stupid Baboons, Stubborn Elephants: A Product Engineer’s Guide to Working with Platform Engineers by Rina Artstain
Testing in Production: the hard parts by Cindy Sridharan
A developer goes to a DevOps conference by Graham King
Inca — Message Tracing and Loss Detection For Streaming Data @Netflix by Allen Wang
Building Audit Logs with Change Data Capture and Stream Processing by Gunnar Morling
All you need to know about caching for serverless applications by Yan Cui
The craft of software development and why it matters by Jakub Holý
Tweet: The corporate IT world is barely working by Martin Thompson
Comparing Database Types: How Database Types Evolved to Meet Different Needs by Justin Ellingwood
Goodbye Microservices: From 100s of problem children to 1 superstar by Alexandra Noonan
Why Google Stores Billions of Lines of Code in a Single Repository by Rachel Potvin and Josh Levenberg
You Are Not Google by Oz Nova
Java agent to detect blocking calls from non-blocking threads. by Project Reactor
The Good Parts of AWS by Daniel Vassallo and Josh Pschorr
OWASP Api Security Top 10, 2019 Edition
A curated collection of awesome resources for the zero-trust security model by Bobby DeSimone
Open Source at AWS

Weekly Links #6 #7

Krzysztof Góralski — Sat, 28 Sep 2019 07:46:27 +0000

Microservices, Monoliths, Architecture, Cognitive Load, DDD

Monoliths Vs Microservices Is Missing The Point—Start With Team Cognitive Load by Team Topologies https://teamtopologies.com/
Software Architecture is Overrated, Clear and Simple Design is Underrated by Gergely Orosz
Sociotechnical DDD by Nick Tune
Organisational Dysfunctions Mirrored as Architectural Complexity by Nick Tune
How do you cut a monolith in half? by tef, programming is terrible
The origin of complexity by Joakim Tengstrand
The boring technology behind a one-person Internet company by Wenbin Fang
Testing Microservices, the sane way by Cindy Sridharan

AWS, GCP, Cloud, Serverless

Uncomfortable @awscloud Truth Corey Quinn
AWS Lambda Pain Points Twitter Thread by Ian Miell
Serverless: 15% slower and 8x more expensive by Einar Egilsson
Cold Starts in AWS Lambda by Mikhail Shilkov
Container-native load balancing on GKE now generally available by Neha Pattan
Google will open a cloud hub in Poland as European growth outpaces rest of world by Elizabeth Schulze

Cloudflare

Introducing Browser Insights by Jon Levine
HTTP/3: the past, the present, and the future by Alessandro Ghedini, Rustam Lalkaka
Workers Sites: Extending the Workers platform with our own serverless building blocks by Ashley Williams
WARP is here (sorry it took so long) by Matthew Prince
Cloudflare architecture and how BPF eats the world by Marek Majkowski

Golang

Introducing Ristretto: A High-Performance Go Cache by Karl McGuire
How to Use Websockets in Golang : Best Tools and Step-by-Step Guide by Aleksandr Ryzhyi
The Bad Go Series by Phil Pearl
Context Package Semantics In Go by William Kennedy
Gomock and Go Routines by Andrew Poydence
Learn Go with tests: Concurrency by Chris James
How we tracked down (what seemed like) a memory leak in one of our Go microservices by Roberto Soares & Christoffer Fjellström
How to work with Postgres in Go by Artemiy Ryabinkov
Better scheduling in Go by Stephen AfamO
Understanding Package Visibility in Go by Gopher Guides, Digital Ocean
Managing Groups of Goroutines in Go by Michal Bock

Security & Privacy

Ah shhgit! Find GitHub secrets in real time by Paul Price
Introducing checkm8 (read "checkmate"), a permanent unpatchable bootrom exploit for hundreds of millions of iOS devices by axi0mX
Centralised DoH is bad for privacy, in 2019 and beyond by Bert Hubert
USENIX Security '19 Playlist

Various

Europe’s Product Management Problem by Siraj Khaliq
81 New Features and APIs in JDK 13 by Simon Ritter
Company culture is… by John Cutler
Enhancing Bandaid load balancing at Dropbox by leveraging real-time backend server load information by Haowei Yuan, Yi-Shu Tai, and Dmitry Kopytkov (Dropbox)
Maximizing Performance with GraalVM by Thomas Wuerthinger
Every Company is Becoming a Software by Jay Kreps
Adventures in the TCP stack: Uncovering performance regressions in the TCP SACKs vulnerability fixes by by Chris Stevens, Michał Switakowski, Ivan Sadikov, Winglung Ngai and Evan Ye
On Sharding by Tim Bray
The One Who Kept VLC Free about Jean-Baptiste Kempf - "You don’t know about networking, yet most of your time is spent on the web, over a network; No matter how good you are at your main focus, this makes you an average developer, and I need good developers."

Weekly Links #5

Krzysztof Góralski — Sun, 15 Sep 2019 17:07:10 +0000

The ONE chart every developer MUST understand by Blaine Osepchuk
Reverse Interview - a list of questions which may be interesting to a tech job applicant by Stanisław Pitucha
Why is DevOps Important? by Jérôme Petazzoni
How Complex Systems Fail - 20 years old document by Richard I. Cook , University of Chicago
An Engineer’s Guide to a Good Night’s Sleep by Nicky Wrightson
Never Alone On Call by Deirdre Mahon
Systems Thinking in Practice by Ryan Frantz
The Power of “Yes, if”: Iterating on our RFC Process by Tanya Reilly
DNS and the Art of Making Systems "Just Complex Enough" by Alex Wilson
Network Architecture Design for Microservices on GCP by Raphael FRAYSSE
Mistake that cost thousands (Kubernetes, GKE) by Gajus Kuizinas
Instrumentation Quality Scores: Guiding You to Better Telemetry Data by Valjean Clark
I test in prod by Charity Majors
Should You Build An API Gateway In-House? by Michał Trojanowski
Confirmation Bias: How your brain wants to wreck your code by Matt Eland
DynamoDB, explained. by Alex DeBrie
AWS Lambda Cold Start Language Comparisons, 2019 edition by Nathan Malishev
How to Manage a Manager? by Yegor Bugayenko
Data Is a Toxic Asset by Bruce Schneier
Google feedback on TypeScript 3.5 by Evan Martin
Golang: Programming with errors by Peter Bourgon
Java: Bean Validation Anti-Patterns by Tom Hombergs
Roguelike Tutorial - In Rust by Herbert Wolverson

Boring Software: New Technology Assessment

Krzysztof Góralski — Tue, 10 Sep 2019 06:32:35 +0000

"Adding new technology to the project is easy, living with it on production is hard." This is why we should "prefer technology that’s well understood, with failure modes that are known".

"Happiness comes from shipping meaningful work."

http://boringtechnology.club/

I have prepared some guidelines / questions to ask yourself to help a little bit with a process of assessment of new technologies (frameworks, libraries, databases etc.) for a project.

Ultimate question: Do you really need this new thing?

Questions to discuss with your team

Is this is really a team decision or we should ask other teams and people inside the company about using it?
Why do you need it? What problem you are trying to solve? Is it right tool for the job? Why it is worth it? (Wrong answers: sexiness, just trying new things)
Will it bring any business value? Can you describe it?
Will it help to deliver project faster or make it more maintainable or with better quality?
How long will it take the ROI?
Why you cannot solve it using existing stack?
Writing custom library, when something exists in Open Source Software? Why?
If you want to use it because of better performance. Do you really need that performance? Can you show the data that it can confirm better performance? (for example, reactive frameworks. We are getting ready for a today's traffic or are we predicting scalability problems that may happen in the long term?)
How popular it is? Is it easy to find people to hire? Is it backed by big companies? Is it easy to find people using that? How many questions on stack overflow? How many people has it in CV on LinkedIn? etc.
Is there someone else in your company using it - how does their use case and findings compare to your use case?
Is it easy to find help? Or you will be learning it by your own? How mature it is?
Is there a Learning Curve? Is it easy to learn? Does your team is able to specify it? Do you think it will be comfortable for the team working with it?
Have you used it in production in the past?
Are there any other companies that are using it on production?
Have you played around with it, create sample application, and have some notes about it?
Is this new thing, another new toy inside your project? Too many tools are hard to maintain.
Is your team experienced with new tool already?
Are you running few services on production? Is it really makes sense to add very different tool in our stack?
How it will affect on your team productivity? Is it easy to find help about it inside your team or company? If you are only one at the team who knows is... it is probably better to avoid it.
Cost estimation, is new solution cheaper/more expensive compared to current one?

Document it.

Good 3rd party libraries

(highly inspired by presentation from Adam Dudczak)

There is documentation
There is access to source code
Big activity inside project & stable release cycles
There is more than 1 maintainer
There are tests or CI tool integrated (check them and coverage)
It is easy to integrate lib with your tests stack
It is top 5 about github stars library - it is recommended to check other similar libs, sometimes top 1 is not the best one
Check issues page. Are there any critical issues? (for example: you can generate same uuid with uuid library) 1.0.0 version released long time ago (it is better to wait for other people to check the bugs for you). Known unknowns vs unknown unknowns. Be careful with fresh tools. Or prepare for contribute to it.
Would be good to pass OWASP dependency check, SonarQube has a plugin for it https://github.com/SonarSecurityCommunity/dependency-check-sonar-plugin
LICENSE (look carefully at GPL!)
There are official docker images
It is easy to find help, stackoverflow, github issues etc.
It has IDE support
It is well integrated with your environment or framework (like our monitoring, linters, CI etc.)
It has clean CVE database

Document it. Try to make a log.

New framework, new database, new language etc.

If you want to make it for POC - Proof of Concept purpose, write it the same way as for production (very often POC are working on production... ) - but it is not recommended to do it for production anyway
Check everything from "Good 3rd party libraries" section
Create sample app with few endpoints, remember about:
- config management
- monitoring, tracing, logs with tools used inside company
- API docs like OpenAPI
- CI/CD, deploy to sandbox
- add linters
- building artifact
- storage connection
- secrets management
- dependency management
- code modularity
- write any kind of tests, unit, integration, e2e, acceptance, with external service
- try to profile/debug your app
- try to do sample load tests
During development, try to create "WTF per hour" Log. (weird & confusing things happened during the development)
Do some notes/results, what was good, what was bad
Another checklist. Does this new thing:
- was it easy to write tests? is there proper tooling? it should be easy to write a test when you call an endpoint of your backend and mock external service
- was it hard to instrument code for monitoring and tracing?
- "allow you to write code that is human readable?, produce code that is optimized for the environment it runs in?, help reduce the size of the application?, allow for the code to be portable and/or extensible?, ensure longevity for the code I am writing?, provide methods to easily test it's APIs are working?" by @steveblue
- are there good tools for debugging/profiling?
- was it easy to create modular code?
- can you compare load tests to something running on production?
Discuss the results it within a team & outside the team

Document it. Try to make a log.

Adding new technology to production

Cost estimation, is new solution cheaper/more expensive compared to current one?
Make a list what do want to achieve to be able to check the results
Add proper monitoring, tracing and good metrics. Make some summaries to check your assumptions.
If you can, create a WTF / per hour/day log, try to log any hard situation - incident management
If you can, create "Is it work?" and log stuff that confirms or not your assumptions
Make some summary every quarter

The End

Usually we can solve problems using existing tools. It is not always worth to add anything new to your stack. Most frameworks are very similar anyway but details matter and usually you don't want to be alone on production and discover new bugs there. New technology should prove that there will be good return of value in future.

Hopefully you will find it useful or you can help me to improve the list :) Happy Coding!

References

The Boring Technology Club by Dan McKinley
The boring technology behind a one-person Internet company by Wenbin Fang
Why I ignore the hype (and you should too) by Steve Belovarich
Good 3rd party library by Adam Dudczak
Image in the background: “Les Refactoreurs” Gustave Caillebotte, Oil on canvas, 1875

Weekly Links #4

Krzysztof Góralski — Sat, 07 Sep 2019 17:21:13 +0000

Operating a Large, Distributed System in a Reliable Way: Practices I Learned by Gergely Orosz
The Product-Minded Software Engineer by Gergely Orosz
What to do once you admit that decentralizing everything never seems to work by Nathan Schneider
The Pipeline Driven Organization - Enabling True Continuous Delivery by Roy Osherove
"It's dead, Jim": How we write an incident postmortem by Fran Garcia
Great Twitter Thread about scaling teams, distributed systems etc. by Andrew Certain @tacertain
Applying the Universal Scalability Law to organisations by Adrian Colyer
A Brief History of “The Span”: Hard to Love, Hard to Kill by Ben Sigelman
Don’t force allocations on the callers of your API by Dave Cheney
Google's Engineering Practices documentation by Google
Elasticsearch is a great example of a modern monolithic application by Daniel Vassallo
Daily Stand-up Injection of Guilt by Yegor Bugayenko, "A 'daily morning stand-up meeting', as it is currently performed, is just a way to manage otherwise undisciplined, non-compliant 'talent', who are reluctant to be organized for the sake of their perceived artistic merit."
Docker: Critical Infrastructure Upgrade Process by Alex Hokanson
8 New Rules of Open Source Infrastructure by Stephan Fabel
Announcing Maesh, a Lightweight and Simpler Service Mesh Made by the Traefik Team
Introducing Fine-Grained IAM Roles for Service Accounts by AWS