Reader

Microservice architecture

• Vibe coding: the good, the almost, and the @#$%**
• Microservices rules #7: Design loosely design-time coupled services - part 2
• Harmel-Law's Architecture Advice Process
• Microservices rules #7: Design loosely design-time coupled services - part 1
• The importance of flow state for developers
• The wrong reasons to adopt microservices
• Microservices rules #10: Make smaller, safer, and reversible changes - part 5
• What developer productivity metrics actually measure
• Only you know what's best for your application
• Writing testable and maintainable JBang scripts
• Upcoming public architecture workshops in 2025: Denver (April/July), and Antwerp (June)
• Microservices rules #11: Track and improve metrics
• Microservices ate my application - an adoption anti-pattern
• The just sharing principle: advice for advice givers
• Microservices rules #3: Apply Team Topologies
• My new LiveProject Series: Deploying Services with Kubernetes
• ISAQB 2024 - Enabling DevOps and Team Topologies Through Architecture: Architecting for Fast Flow
• Loose design-time coupling: part of the wiring of a winning organization
• Microservices rules #10: Make smaller, safer, and reversible changes - part 4
• Reducing insider trading in a microservice architecture
• The evolution of the Microservice Architecture pattern language
• Microservices: the symphony
• Microservices rules #10: Make smaller, safer, and reversible changes - part 3
• Microservices rules #10: Make smaller, safer, and reversible changes - part 2
• Architectural patterns for modular monoliths that enable fast flow
• New premium post: Building a business case for reducing technical debt
• Microservices rules #10: Make smaller, safer, and reversible changes - part 1
• Architecting microservices for fast, sustainable flow
• Evolving an architecture: a problem solving-driven approach
• Architecting monoliths for fast, sustainable flow
• Work smarter, not longer: Embrace fast flow
• The pattern format: an antidote to hype
• Eliminating tedium with OpenRewrite
• Microservices rules #5: Deliberative decision making
• Upcoming public architecture workshops
• GenAI application development - a Cynefin perspective
• Public architecting for fast, sustainable flow workshops in September 2024
• Premium post: making sure that buying is really better than building
• Microservices rules: what good looks like - July 2024 edition
• Upcoming architecture workshops and talks in Europe in November 2024
• Keynote: Enabling DevOps and Team Topologies thru architecture: architecting for fast flow
• STOP hurting yourself by doing big bang modernizations!
• Did you refactor a monolith to microservice? How did it go?
• I'm now a Team Topologies Advocate! 🎉
• Premium post: There's more to a microservice architecture than services
• PLoP: the gathering of the patterns community
• A better way to think about developer productivity metrics
• How do you structure your traditional (non-modular) monolith applications?
• Implementing Faramir with Spring AI
• How modular can your monolith go? Part 7 - no such thing as a modular monolith?
• New premium post: Doing more with less, part 3 - Buy don't build using Wardley Mapping
• Using GenAI (Github Copilot) to build a GenAI service
• Dissecting 'architecting for fast, sustainable flow'
• New premium post: Doing more with less, part 2 - Buy don't build using DDD
• Architecture is multi-dimensional
• The success triangle reinterpreted: it's all about fast flow
• New premium post: Doing more with less, part 1: Improving the developer experience
• Announcing Faramir: an LLM-powered microservice for validating phone numbers