Recently I joined Lukas Egger on SAP Signavio’s Process Transformers podcast to talk about what makes software adaptable in a world that’s only getting faster and more chaotic. Here’s a brief summary of some key points we discussed. --- Architecture is about change Good architecture isn’t just about runtime qualities like scalability or availability. It also shapes how easy it is to change software tomorrow based on what we build today. Software must satisfy two constituencies: its us...| Microservice architecture
I’ve just started working on the next article in the series about authentication and authorization in a microservice architecture. In contrast with part 3 and part 4, which describe hand-coded authorization logic, this article will explore a declarative approach using Oso Cloud as an external authorization service. I’ve just committed some changes to the RealGuardIO example application that Defines an Oso Cloud policy document which captures the authorization rules for who can disarm a se...| Microservice architecture
I am excited by Susanne Kaiser’s new book, Architecture for Flow: Adaptive Systems with Domain-Driven Design, Wardley Mapping, and Team Topologies. Here’s my Amazon review: An important, must-read book. In today’s volatile world, businesses must adapt quickly—and IT must keep pace. This book shows how to do that with three powerful tools: DDD, Wardley Mapping, and Team Topologies. Buy it, read it, and put it into practice. I encourage you to read it too.| Microservice architecture
This article is the fourth in a series of articles about authentication and authorization in a microservice architecture. The complete series is: Overview of authentication and authorization in a microservice architecture Implementing authentication Implementing JWT-based authorization Implementing authorization using fetch and replicate Implementing complex authorization using Oso Cloud - part 1 Implementing complex authorization using Oso Cloud - part 2 In Part 3 - implementing authorizatio...| Microservice architecture
Microservices rules #4: Provide a great developer experience This article continues the series on microservices rules: what good looks like, a collection of principles and practices that help teams adopt microservices successfully. The articles in the series are: 1. Practice continuous delivery/deployment 2. Implement fast, automated deployment pipelines 3. Apply Team Topologies 4. Provide a great developer experience (DevEx) 5. Use a deliberative design process 6. Design independently deploy...| Microservice architecture
If you’ve spent any time developing with Claude Code, you’ve probably noticed a frustrating pattern: it often forgets to run all the tests — or worse, ignores test failures entirely — and attempts to commit broken code. This article shows a simple way to stop that from happening. I’ll describe how I tried to require the tests to pass with a Git pre-commit hook, why that wasn’t enough, and how I ultimately needed to deny Claude Code direct access to git commit. Background To unders...| Microservice architecture
This article continues the series on microservices rules: what good looks like, a collection of principles and practices that help teams adopt microservices successfully. The articles in the series are: 1. Practice continuous delivery/deployment 2. Implement fast, automated deployment pipelines 3. Apply Team Topologies 4. Provide a great developer experience (DevEx) 5. Use a deliberative design process 6. Design independently deployable services 7. Design loosely coupled services - part 1, pa...| Microservice architecture
This article is the third in a series of articles about authentication and authorization in a microservice architecture. The complete series is: Overview of authentication and authorization in a microservice architecture Implementing authentication Implementing JWT-based authorization Developing complex authorization Implementing complex authorization using Oso Cloud - part 1 Implementing complex authorization using Oso Cloud - part 2 The previous article described how to implement authentica...| Microservice architecture
It’s been a few months since I wrote the first article of this series, and, remarkably, AGI is still work-in-progress. But recently, I read this interesting 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. Installing Helpfully, its home page tells you how to install it, simply npm install -g @anthropic-ai/claude-code. Less helpfully, the executable isn’t called claude-co...| Microservice architecture
This article continues the series on microservices rules: what good looks like, a collection of principles and practices that help teams adopt microservices successfully. The articles in the series are: 1. Practice continuous delivery/deployment 2. Implement fast, automated deployment pipelines 3. Apply Team Topologies 4. Provide a great developer experience (DevEx) 5. Use a deliberative design process 6. Design independently deployable services 7. Design loosely coupled services - part 1, pa...| Microservice architecture
Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities. The microservice architecture enables the continuous delivery/deployment of large, complex applications. It also enables an organization to evolve its technology stack.| microservices.io
About Microservices.io| microservices.io
About Microservices.io| microservices.io
About Microservices.io| microservices.io
About Microservices.io| microservices.io
