iiinova — where your digital self keeps evolving

Chris Richardson @crichardson.bsky.social · 04/10/2025

Deal of the Day October 4: Save 45% on my book Microservices Patterns, Second Edition, and other selected titles @ManningBooks

140

Chris Richardson @crichardson.bsky.social · 24/09/2025

Today (Sept 24 PT) my publishing, Manning, has a sitewide eBook sale. Most notably, you can get the MEAP of Microservices Patterns, 2nd edition for 50% off.

130

Chris Richardson @crichardson.bsky.social · 11/09/2025

My new article "Claude Code: Allow Bash(git commit:*) considered harmful" describes how I put in place guardrails to prevent this. bit.ly/41IGTQP

020

Chris Richardson @crichardson.bsky.social · 11/09/2025

If you’ve used Claude Code, you’ve probably seen it happily commit broken code. Perhaps it skipped running the tests. Or, it mades excuses about why failing tests are ok.

130

Chris Richardson @crichardson.bsky.social · 04/08/2025

I've written another article in the series on microservices rules - what good looks like, a collection of principles and practices that help teams adopt microservices successfully. Microservices rules #9 is Develop observable services, the fourth of four architectural rules:

120

Chris Richardson @crichardson.bsky.social · 23/07/2025

Wow. Thanks for buying the MEAP of Microservices Patterns, 2nd edition.

130

Chris Richardson @crichardson.bsky.social · 10/07/2025

It’s been a few months since I wrote about 'vibe' coding, but remarkably, AGI is still work-in-progress. I recently read an article, which described using Claude Code to ‘beautify’ a UI. Having just implemented an ugly NextJs-based UI, I thought I’d try using Claude Code to improve it.

140

Chris Richardson @crichardson.bsky.social · 04/07/2025

My publisher - Manning - has a big sale this long weekend. It's a great opportunity to get the MEAP for Microservices Patterns, 2nd Edition at a discount.

130

Chris Richardson @crichardson.bsky.social · 27/06/2025

Learn more: microservices.io/post/archite...

000

Chris Richardson @crichardson.bsky.social · 27/06/2025

Just in time for the weekend: I am very excited to announce that the MEAP for the second edition of my book, Microservices Patterns, is now available! It’s something I’ve been working on for quite some time, and pleased that I can finally share it with you.

110

Chris Richardson @crichardson.bsky.social · 23/06/2025

I recently gave a talk at the excellent #DDDEurope 2025 conference in Antwerp, where I discussed the synergistic relationship between #teamTopologies and the #microserviceArchitecture.

110

Chris Richardson @crichardson.bsky.social · 21/05/2025

I've written a new article: Microservices rules #8 - design independently deployable services. It describes why independently deployability is essential, what goes wrong when you ignore, and how to achieve it. premium.microservices.io/microservice...

premium.microservices.io

Microservices rules #8: Design independently deployable services

This is another article in the series about microservices rules: what good looks like, which are a set of principles and practices for using microservices effectively. The articles in the series are:…

000

Chris Richardson @crichardson.bsky.social · 21/05/2025

Independently deployable services is a defining characteristic of the microservice architecture. Yet many companies ignore the concept. As a result, they fail to realize many of the benefits of the microservice architecture.

310

Chris Richardson @crichardson.bsky.social · 08/05/2025

Same word, different contexts => different meaning #GenAI

221

Chris Richardson @crichardson.bsky.social · 07/05/2025

New article: Microservices platforms: when team topologies meets microservices patterns - an introduction

140

Chris Richardson @crichardson.bsky.social · 30/04/2025

I've written the first article in a series of in-depth articles about authentication and authorization in a microservice architecture. microservices.io/post/archite...

microservices.io

Authentication and authorization in a microservice architecture: Part 1 - Introduction

153

Chris Richardson @crichardson.bsky.social · 25/04/2025

Coincidentally, that's what ChatGPT said. 😀

000

Chris Richardson @crichardson.bsky.social · 24/04/2025

To learn more about Github Copilot's hallucinations, please read the latest installment of Vibe coding: the good, the almost, and the @#$%** microservices.io/post/archite...

microservices.io

Vibe coding: the good, the almost, and the @#$%**

Public workshops:

000

Chris Richardson @crichardson.bsky.social · 24/04/2025

Yesterday, I needed to convert a draft article from Asciidoc to Markdown. I asked Github Copilot: "How to convert Asciidoc to Github markdown?" It didn't go well.

200

Chris Richardson @crichardson.bsky.social · 23/04/2025

Need help with your architecture? I’m available. I provide consulting and workshops. chrisrichardson.net

011

Chris Richardson @crichardson.bsky.social · 23/04/2025

In the meantime, here's a link to a series of articles about modular monoliths. microservices.io/post/archite...

microservices.io

How modular can your monolith go? Part 1 - the basics

Public workshops:

100

Chris Richardson @crichardson.bsky.social · 23/04/2025

The problem is that successful applications and their organizations tend to grow. Ultimately, they can outgrow the monolith architecture for reasons I'll explain in a follow up post.

100

Chris Richardson @crichardson.bsky.social · 23/04/2025

Also, in order to reduce test execution time during local development and the deployment pipeline, the source code should be organized into build projects in a way that minimizes build-time coupling.

100

Chris Richardson @crichardson.bsky.social · 23/04/2025

Teams can work independently and productively on their domain modules with minimal coordination

100

Chris Richardson @crichardson.bsky.social · 23/04/2025

Microservice architecture basics - part 4 For many applications that need to be developed using fast flow, the modular monolith is a good choice of architectural style. A modular monolith is structured as a collection of loosely design-coupled, domain-oriented modules.

220

Chris Richardson @crichardson.bsky.social · 11/04/2025

When an organization migrates their monolith to microservices, the correct approach is to focus on defining the services. They should adopt Team Topology's Thinnest Viable Platform approach, and evolve the platform to handle the actual unmet needs of the services.

110

Chris Richardson @crichardson.bsky.social · 11/04/2025

Back in 2019, I wrote about several anti-patterns of microservices adoption. One of those anti-patterns is "Focussing on technology". Organizations focus on the underlying technology, especially deployment tech, rather than services. Using today's terminology it's "Focus on platforms".

130

Chris Richardson @crichardson.bsky.social · 31/03/2025

Microservice architecture basics Here's a summary of what I've covered so far.

110

Chris Richardson @crichardson.bsky.social · 27/03/2025

The other two architectural properties are testability and deployability, which together ensure a short lead time - the time from commit to deploy.

100

Chris Richardson @crichardson.bsky.social · 27/03/2025

Microservice architecture basics - part 3 DevOps and Team Topologies require an architecture with three key properties. The first property is loose design-time coupling: a change to an element owned by one team does not regularly require lock step changes to elements owned by other teams.

121

Chris Richardson @crichardson.bsky.social · 26/03/2025

Please read my new article to learn more about the architecture advice process, its relationship with fast flow, and how loose design-time coupling leads to faster decisions. microservices.io/post/archite...

microservices.io

Harmel-Law's architecture advice process and fast flow

Public workshops: Designing microservices: responsibilities, APIs and collaborations:

040

Chris Richardson @crichardson.bsky.social · 26/03/2025

The architecture advice process is a refreshing and superior alternative to traditional architecture practices. Most notably, it promotes team autonomy and faster decision-making, both of which are essential for fast flow.

110

Chris Richardson @crichardson.bsky.social · 26/03/2025

I’m a fan of Andrew Harmel-Law’s book Facilitating Software Architecture. It’s a must-read for anyone who wants to improve their architecture skills. One of the many gems in the book is the ‘Architecture Advice Process’. It describes how an organization should make architectural decisions.

131

Chris Richardson @crichardson.bsky.social · 25/03/2025

Microservice architecture basics - part 2 Fast flow requires the fast flow success triangle. It's comprised of three elements: process organization and architecture. The first two elements are: * Process: DevOps as defined by the DevOps handbook * Organization: as defined by Team Topologies

110

Chris Richardson @crichardson.bsky.social · 24/03/2025

The solution is fast flow: The continuous delivery of a stream of small changes to production/users that results in continuous feedback from production/users.

100