View this email in your browser

Dear Architect,

Welcome back to our weekly issue!
First of all, I'd like to wish Merry Xmas to you and your family, after this challenging here we deserve some holidays staying with the people we love.

This week we have a special edition, I thought would be great to select 5 books that every architect should read despite you are wearing many hats at work including the architect one or you are a professional with many years of experience.

My selection is not merely focused on architecture practices but also on how architecture impacts other aspects of an organization.

Enjoy the read and see you next week!

Software Architecture

Fundamentals of Software Architecture

This book provides the first comprehensive overview of software architecture’s many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics.

Software Architecture

Monolith to Microservices

How do you detangle a monolithic system and migrate it to a microservices architecture? How do you do it while maintaining business-as-usual? As a companion to Building Microservices, this new book details multiple approaches for helping you transition from existing monolthic systems to microservice architectures. This book is ideal if you're looking to evolve your current systems, rather than just rewriting everything from scratch.

Engineering Practices

Team Topologies

Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns.
In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams
Software Architecture

Building Evolutionary Architectures

The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time.
Engineering Practices


For years, we’ve been told that the performance of software delivery teams doesn’t matter—that it can’t provide a competitive advantage to our companies. Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.

Thanks for reading Dear Architects 🙏

If you have any suggestions to make this newsletter better, just drop us an email!

Have a great rest of the week 😉

We just need a few minutes of your time to make Dear Architects even better
Sure! Let me share what I think about Dear Architects!
Copyright © 2020 deararchitects, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp