Principles

Failure Isolation

Part 5 of my “Responsible Microservices” series is live! Should that be a Microservice? Part 5: Failure Isolation In the first part of this series, we laid out a set of principles to help you understand when microservices can be a useful architectural choice. We promised follow-up pieces describing each of the factors in more detail. In the fifth post of the series, we explore failure isolation. Digital products don’t live alone.

Thinking Architecturally Podcast

Thinking Architecturally Book

I’m very excited to announce my latest book project, Thinking Architecturally, is now available! My thoughts on being an architect, dealing w/ change, etc. If you’ve attended one of my talks in the last few years, you will recognize some of the material. The reception has been beyond my expectations and I am delighted by the responses I’ve received from people that have read the book. If you are interested in perusing the material, it is a free download from the Pivotal Resource center.

Thinking Architecturally Is Available

I’m very excited to announce my latest book project, Thinking Architecturally, is now available! My thoughts on being an architect, dealing w/ change, etc. If you’ve attended one of my talks in the last few years, you will recognize some of the material. The reception has been beyond my expectations and I am delighted by the responses I’ve received from people that have read the book. If you are interested in perusing the material, it is a free download from the Pivotal Resource center.

Independent Scalability

Part 4 of my “Responsible Microservices” series went live yesterday! Should that be a Microservice? Part 4: Independent Scalability In the first part of this series, we laid out a set of principles to help you understand when microservices can be a useful architectural choice. We promised follow-up pieces describing each of the factors in more detail. In the fourth post of the series, we explore independent scalability. Let’s take a quick spin in our hot tub time machine and head back to an era before cloud, microservices and serverless computing.

Independent Life Cycles

Part 3 of my “Responsible Microservices” series went live earlier this month! Should that be a Microservice? Part 3: Independent Life Cycles In the first part of this series, we laid out a set of principles to help you understand when microservices can be a useful architectural choice. We promised follow-up pieces describing each of the factors in more detail. In the third post of the series, we explore independent life cycles.

Multiple Rates of Change

Part 2 of my “Responsible Microservices” series went live last week! Should that be a Microservice? Part 2: Multiple Rates of Change In the first part of this series, we laid out a set of principles to help you understand when microservices can be a useful architectural choice. We promised follow-up pieces describing each of the factors in more detail. Here’s the first of such posts; let’s explore multiple rates of change.

Please Microservice Responsibly

I wrote a post summarizing some advice that Matt Stine and I used with a client… Should that be a Microservice? Keep These Six Factors in Mind You’re writing more code than ever before. The trick is knowing what should be a microservice, and what shouldn’t. These days, you can’t swing a dry erase marker without hitting someone talking about microservices. Developers are studying Eric Evan’s prescient book Domain Driven Design.