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.

Same word, different contexts => different meaning #GenAI

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...

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.

Manning's Patrick's Day sale finishes soon!

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.

Excellent

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.

I often see teams adopting microservices for all the wrong reasons. Here are three of the most common yet misguided reasons for adopting the microservice architecture.

These days, there’s a lot of interest in measuring developer productivity. And rightly so since there’s a strong correlation between high performance software delivery and business success. Yet, I think there's a couple of problems with the so-called developer productivity metrics.

This weekend my publisher Manning has a Valentine's day sale: HALF OFF all books & all liveProjects and liveVideos $10 each Lot's of last minute gifts for that special person in your life.

Software architecture is all about making decisions. For example, you need to select an architecture style - monolith vs. microservices. You also need to select the numerous elements of your technology stack. And so it goes on…

I have a few public workshops (at conferences) this year: ExploreDDD Denver in April, DDD EU Antwerp in June, and UberConf Denver in July. And as always, I’m available for private workshops and consulting engagements at your company.

I regularly write scripts to automate various tasks. After first using Bash and then Python, I am now writing scripts in Java using JBang. This article describes how I’ve been writing testable and maintainable JBang scripts

How many billions have been invested in GenAI? Yet another reminder that it's still fact-challenged and you must verify its output.

I've written a new article in the series about microservices rules: what good looks like, which are a set of principles and practices for using microservices effectively. This article describes three categories of metrics you should track to ensure your microservices development stays on course.

It’s been a while since I’ve written about anti-patterns of microservices adoption. These days, however, I often encounter a previously undocumented anti-pattern that I’ve named Microservices ate my application.

Quick question: what grammar checker are you using? I'm writing in Asciidoc in either Visual Studio Code or Intellij IDEA I've found Jetbrains Grazie Pro to be very helpful and convenient. Any other suggestions?

Learn about the service collaboration patterns - Saga, API Composition, CQRS - in my online, self-paced bootcamp. Available for the discounted price of USD $95 - limited time only. Learn more and enroll: https://buff.ly/3a3uyMo

Manning is having a sale on Wednesday January 29th starting at 12.10 am ET and ending at midnight PT. All liveProjects are $10. My two liveProject series (four projects each) cover key aspects of developing a microservices-based application.

I've written a new post: Microservices rules #3 - Apply team topologies. It's another article in the series: Microservices rules: what good looks like

On Wednesday, January 22, 2025 at 6pm, I'll be giving a talk in Melbourne Australia. I hope to see you there. The talk is: Enabling DevOps and Team Topologies: Architecting for Fast Flow

The Eventuate Platform has a new getting started guide for @SpringBoot-based applications:

Learn about the service collaboration patterns - Saga, API Composition, CQRS - in my online, self-paced bootcamp. Available for the discounted price of USD $95 - limited time only. Learn more and enroll: https://buff.ly/3a3uyMo

If only there was an company that produces software agents that could replace sales people... 🤔 --- Salesforce will hire 2,000 people to sell AI products, CEO Marc Benioff says

When this popped up at the start of NVIDIA CEO Jensen Huang Keynote Speech at CES 2025, I thought I was about to see something shockingly NSFW. Seriously, despite all the hype, it's important to remember that true intelligence still biological.

Learn about the service collaboration patterns - Saga, API Composition, CQRS - in my online, self-paced bootcamp. Available for the discounted price of USD $95 - limited time only. Learn more and enroll: https://buff.ly/3a3uyMo

I've written a new post for paid subscribers. It's part of the series of articles about Microservices Rules: what good looks like. This article describes rule #1: practice continuous delivery