Deal of the Day October 4: Save 45% on my book Microservices Patterns, Second Edition, and other selected titles @ManningBooks
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.
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.
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:
Wow. Thanks for buying the MEAP of Microservices Patterns, 2nd edition.
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.
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.
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.
I recently gave a talk at the excellent #DDDEurope 2025 conference in Antwerp, where I discussed the synergistic relationship between #teamTopologies and the #microserviceArchitecture.
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.
New article: Microservices platforms: when team topologies meets microservices patterns - an introduction
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...
Authentication and authorization in a microservice architecture: Part 1 - Introduction
Authentication and authorization in a microservice architecture: Part 1 - Introduction
microservices.io
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.
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.
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".
Microservice architecture basics Here's a summary of what I've covered so far.
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.
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.
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
Microservice architecture basics - part 1 Today's world is volatile, uncertain, complex and ambiguous (VUCA). If you release infrequently, you risk building the wrong application the wrong way.
I recently added support for Async API to the Eventuate Platform. While doing so, I implemented some new messaging APIs (events, commands, sagas) that enable the generation of more comprehensive API metadata.
I've written a new article: Microservices rules #7: Design loosely design-time coupled services - part 1 It describes the concept of design-time coupling and why loose design-time coupling is essential in a microservice architecture.
Modernizing your architecture? Send your team to ExploreDDD to learn the skills that they need. Workshops on event storming, DDD, the microservice architecture, modernization strategies and more.
I'm currently doing some writing (Asciidoc in Visual Studio Code) and got tired of switching to the shell to rebuild the PDF after making a change. So I asked Github Copilot: How to define the build task for a workspace? The answer: define a task in .vscode/tasks.json.
Using Collectors.groupingBy() with Collectors.collectingAndThen() is a handy way to transform a list into a map. In this example, collectingAndThen() computes each map entry's value by passing a group of list elements to a function.
Flow state—or more precisely, abundant flow—is one of the three key elements of a great Developer Experience (DevEx). Yet, in today’s world, it’s increasingly difficult to achieve.
Majorama 1 is a quantum processor powered by topological qubits. How many qubits does it have? What kind of processing can it do? I'm asking for a friend.