К основному контенту


Сообщения за август, 2018

5 за 5 (история 9)

Вот не поймешь, хвалят коллеги или ругаются... (с) 1. "Punishing failure makes it worse. Unshared failures are the experience of one individual. They are not institutional learning." ( by Jessica Kerr  tweet ) 2. The problem with root cause analysis is there’s always going to be another root cause. Robustness happens at a higher level. And resilience at a higher level still. (by Jessica Kerr tweet ) 3. Очередная история про Git от Сергея Сергеева, беседа в подкасте "Подлодка" . Напомню ссылку на отличную лекцию Сергея. 4. " Тимлид — это сержант в IT-подразделении " - хорошее интервью с Романом Ивлиевым. 5. Неплохая панелька тимлидов с инсайдами из известных компаний.   Отлично смотрится на скорости х1.5

5 за 5 (история 8)

И снова с вами рубрика "что интересного было в ленте на этой неделе". 1.  Building and Testing Resilient Web Applications with Toxiproxy. Статья , видео . "A resilient system is one that functions with one or more components being unavailable or unacceptably slow. Applications quickly become intertwined with their external services if not carefully monitored, leading to minor dependencies becoming single points of failure. For example, the only part of Shopify that relies on the session store is user sign-in - if the session store is unavailable, customers can still purchase products as guests. Any other behaviour would be an unfortunate coupling of components. This post is an overview of the tools and techniques we used to make Shopify more resilient in preparation for the holiday season." 2. What is Soak Testing ? "Soak testing (otherwise known as endurance testing, capacity testing, or longevity testing) involves testing the system to detect the pe

5 за 5 (истории 6-7)

Последняя неделя отпуска прошла в режиме "без связи", поэтому предыдущий выпуск пропустил. В этом нагоняем, продолжая читать " Just Enough Software Architecture " и добавив интересных ссылок. 1. Работа команды над решением задачи снижения риска ухудшения архитектуры путем прояснения текущего ее состояния для новых членов команды: we were aware of providing coverage of the three primary models — the domain, the design, and the code models —and also the three primary architectural viewtypes — the module, runtime, and allocation views . We started with the easiest documentation to produce and gradually added in more expensive parts. After each one, we asked ourselves if the risk had substantially reduced and we calibrated that evaluation based on our coverage of the viewtypes and models. When possible, we built representative and textual models rather than fully general and graphical ones. We decided to create a graphical model of our modules and component asse