this post was submitted on 18 Oct 2024
46 points (100.0% liked)

Programming

17343 readers
270 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
46
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]
 

I just finished reading this book and decided to share my experience with it.

About the Book

Continuous Architecture in Practice is a sequel to Continuous Architecture both written by Murat Erder, Pierre Pureur, and Eion Woods. The authors attempt to address feedback from their 1st book by navigating the reader through the Trade Financs eXchange (TFX) case study.

The book starts with a brief introduction to the core concepts of Continuous Architecture, including its 6 principles, as well as its essential activities:

  1. Focus on quality attributes
  2. Drive architectural decisions
  3. Know your technical debt
  4. Implement feedback loops

From then on the book switches focus to common architectural concerns:

  1. Data
  2. Security
  3. Scalability
  4. Performance
  5. Resilience
  6. Emerging Technologies

Each concern is tackled in a separate chapter that features an introductory quote, a definition along with some historical context, a list of issues an someone should keep in mind when architecting for that concern, a list of tactics, and a further reading section.

My Opinion

Overall, I liked reading the book, it gave me a lot of inspiration and a desire to learn more about particular topics. The book assumes a certain level of familiarity with software engineering which helps it focus on general concerns and avoid implemention specific details.

I particularly liked the Emerging Technlogies chapter as it offers a healthy view on AI, ML, and shared ledgers. It helps remove the fairy dust that's blinding our industry, and instead focuses on meaningful changes that actually provide value to a product.

Also, as someone with experience in software security I appreciated the focus on shifting left security concerns.

Who Should Read This

In my opinion, every software engineer can benefit from reading this at some point in their career. However, I wouldn't recommend it to a junior, if you are not already familiar with the topics covered in the book it could be intemediating.

PS I am not affiliated with the book or its authors in any way. I am just a person that read a book they liked wanted to share my experience.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 8 points 2 weeks ago (1 children)

Is anyone interested in starting a book club? Right now I am reading "Implementing Domain-Driven Design" by Vaugn Vernon.

[โ€“] [email protected] 1 points 2 weeks ago

I would totally be down for this. I am currently reading zero trust networks (2nd edition), but this is mainly due to the company I am working for looking to open up some web apps to the public internet. I am also reading Net Zeros and Ones to look more at data sanitizing.

Then fun reading is 2001 a space Odyssey.