This Monday, we conducted the fourth stream of the Code of Architecture Club's book, "Continuous Architecture in Practice."

This Monday, we held fourth-stream Code of Architecture Club by the bookContinuous Architecture in Practice" It was largely about resilience, but we also talked about emerging technologies and drew conclusions from the book. Actually, the whole discussion was around reliability, fault tolerance, resilience as an architectural characteristic. I've written about this glava before. stand-off.

We had two guests.

• Evgeny Peshkov, techlid, independent expert and consultant, passionate about creating products, building effective teams and implementing technical excellence practices in the world of software development and architecture, founder of the community DDDevotion. Sergey Baranov, architect, founder of the conference ArchDays. Sergey conducts channels

During the discussion, we mentioned additional materials.

• My article.Designing reliable systems - is the game worth the candle", which is entirely devoted to the topic of reliability
• "Site Reliability Engineering" - a book from the guys at Google, which began a series of SRE books and they talk about the process in General.
• "Building Secure and Reliable SystemsA book from the guys at Google, where they talk about the principles of designing reliable systems (Continue reading series of SRE books)
• "AWS Fault Isolation BoundariesAn interesting white paper from AWS on the boundaries of failure isolation in AWS (Infrastructure abstractions: zones, regions, globl, as well as the separation of control plane and data plane in the design of services and the concept of static stability)
• "A Model-based, Quality Attribute-guided Architecture Re-Design Process at GoogleAn interesting white paper from the guys from Google, which shows how the system will be redesigned to improve its reliability, and the redesign itself is performed formally enough to assess the positive impact on reliability on the model.
• "Deployment Archetypes for Cloud ApplicationsAn interesting white paper from the guys from Google, in which they talk about different models of deployment applications that allow you to reach different levels of availability. (zonal, regional, multiregional, global, hybrid, multicloud)
• "Philosophy of Software DesignA great book on how to deal with complexity.
• "503 Podcast - System Design in terms of reliabilityPodcast with Andrey Dmitriev from JUG Ru Group, where I was a guest and we discussed the design of reliable systems
• "Architecting for Scale: High Availability for Your Growing ApplicationsLee Atchison is an interesting book where he discusses design for scaling and issues of accessibility. The book survived the second edition and it was good for her.
• "SRE: Troubleshooting and System DesignMy article is about hiring SRE engineers at Tinkoff, and the type of interview in which we put engineers to the test.
• "Public interview on troubleshooting for SRE engineers at the Devoops conferencePublic interview with the incident
• Cool report "Patterns of fault-tolerant architecture" The guys from Yandex about fault-tolerant systems
• Sergei Baranov's speechHow to Make Engineering Decisions in Uncertainty- mentioned in connection with the principles of the whole book "Continuous Architecture"
• Miro board with all of our slides that we've been showing. 4 series

#Software #Architect #SystemDesign #Philosophy #SoftwareArchitecture #Processes #Management #SRE #Reliability #DistributedSystems