Skip to content
#BookCube

Code of Architecture - Happy New Year

#BookCube

This year, Code of Architecture has continued its mission of spreading knowledge about design and architecture. We had time to discuss five books over the year, each of which gave something to the audience:

  • Distributed systems A fundamental book on distributed systems from Tanenbaum and van Steen. The book is very good for structuring your knowledge and deep immersion in the world of distributed systems. If there were actual examples in the book, it would be completely out of competition. An overview of the book is available in my article;
  • A Philosophy of software design One of the rare books that are written clearly, but contain the word philosophy in the title. John Osterhut shares his thoughts on the development of software and wants to listen to him, as you can see the depth of study and experience of the author, who taught for many years at Stanford and is a co-author of the Raft consensus algorithm. An overview of the book is available in my article;
  • Building evolutionary architecture A book with an interesting concept of applying an evolutionary approach to architecture. Unfortunately, the authors have not advanced much beyond the concept. A general overview is available in my article;
  • Kubernetes patterns A good book for developers about the primitives of Kubernetes. But the difference here is that the feed comes from application scenarios that interest the people designing the applications, rather than those who support the K8s itself. This view makes the book very useful. A general overview is available in my article;
  • Continuous architecture in practice A good review book with a cool set of principles, which, when immersed in depth, is empty, but contains a lot of references to other materials. A general overview is available in my article.

And here are the wishes for you for the next year, which we drew from these books:

  • Make your distributed system so it’s not embarrassing to show it to Andrew Tanenbaum.
  • Use strategic programming as taught by John Osterhut
  • Remember the evolution of systems and their architecture, and not be left behind by Charles Darwin.
  • Use K8s not because you were forced to, but because it helps your system solve the standard problems that Bilgin Ibryam, Roland Huss wrote about.
  • Use not only CI/CD (continuous integration/delivery)but also follow CA principles (Continuous architecture)which sound good on paper.

Do not lose interest in self-development, read good books and apply what you read in practice to consolidate knowledge. All this will allow you to become a better engineer and more effective in playing the role of an architect if you have to do it.

P.S. And this year, we held several specials based on whitepapers.

And in the new year, I personally recommend that you start reading more whitepapers – they have more content and are much denser than regular books:)

Happy New Year!