This Monday, we hosted the first Code of Architecture stream of our new book, Continuous Architecture in Practice. In this issue, we discussed topics.

This Monday, we held first-stream Code of Architecture Club's new bookContinuous Architecture in Practice. In this issue, we discussed topics. The importance of architecture here and now, and specifically the challenges that architects face, and then how continuous architecture will help with them. ||In fact, no, the challenges were separate, and the principles of continuous architecture were separate.||

• about making and governing architectural decisions, about quality attributes, technical debt, about feedback cycles (Fitness function, continuous testing)Models and notations to describe architecture, design patterns and architectural styles, the concept of architecture as a stream of decision-making. ||Here, too, all this was not seamlessly united by a cross-cutting idea, which shows that the authors did not quite succeed in designing a consistent chapter in content.|| The guest of the stream was Maxim Smirnov – IT architect and author "The architecture of IT solutions."

At the very issue, we mentioned books:

• Building Evolutionary Architecture stripper It's in CoA. Technology Strategy Patterns - now stripper It's in CoA.
• Continuous Architecture: Sustainable Architecture in an Agile and Cloud-Centric World A previous version of the book, which later became Continuous Architecture in Practice.
• Vernon's book series Addison-Wesley Signature Series (Vernon)Continuous Architecture in Practice

Separately, we discussed that Continuous Architecture is a good naming for a theme. Then I went to continuous-architecture.org and found a set of documents that stuck to the theme of continuous architecture:

• manifesto agile manifesto
• framework Toolkit for Continuous Architecture in Organizations
• instruction How to implement it in organizations

#SoftwareArchitecture #DistributedSystems #Architecture #SystemDesign #Software #CoA