---
title: "Why I'm No Longer Talking to Architects About Microservices"
url: https://daily.dev/posts/why-i-m-no-longer-talking-to-architects-about-microservices-ltjl3nkaw
source_url: https://blog.container-solutions.com/why-im-no-longer-talking-to-architects-about-microservices
type: article
source: "Container Solutions"
published: 2025-03-11T15:35:43.748Z
updated: 2025-03-11T15:36:09.693Z
tags: ["devops", "architecture", "microservices", "agile"]
reading_time: 7
upvotes: 227
comments: 11
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why I'm No Longer Talking to Architects About Microservices

**[Container Solutions](https://daily.dev/sources/containersolution)** · 7 min read · 227 upvotes · 11 comments

## Summary

Microservices discussions are often unproductive due to unclear definitions, abstract conversations disconnected from business goals, and lack of necessary organizational changes. Instead of focusing on microservices as an end, it's crucial to address concrete challenges like faster feature deployment, reducing system coupling, and scaling efficiently. Effective microservices implementation requires cross-functional, autonomous teams and a mature DevOps culture. Organizational change is harder than software change and essential for microservices' success.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.container-solutions.com/why-im-no-longer-talking-to-architects-about-microservices>

## Community discussion

Top comments from developers on daily.dev.

**@dave28** · 17 upvotes

> "If you listen closely, many of these conversations about microservices are not actually about architecture, but about wanting to work for a different company, where technology is cutting-edge and problems are theoretically interesting, rather than legacy-ridden and constrained by real-world trade-offs."
>
> Great line.

**@shakes268** · 10 upvotes

> I'm an architect and I read this so I'm sorry I broke your rule.

**@superpt** · 1 upvotes

> Good post, but I have a question. So how do you approach in distributed system, messaging implementations?
> Mono talking with it self with a queue in the middle? Would love to see your "solution" for never talking about this again.

**@manhvu** · 1 upvotes

> > a mature DevOps culture
>
> agree, we moved to microservices but we can't even hail the devops guy to help us investigate the issue when a service is down. "Will put that in the backlog" they say...

**@richardgreen** · 1 upvotes

> We've stopped referring to Microservices where I work, instead we've just gone back to SOA.
>
> Now, where has my book on CORBA gone?

## Similar posts on daily.dev

- [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments
- [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments
- [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments

---

Tags: [#devops](https://daily.dev/tags/devops), [#architecture](https://daily.dev/tags/architecture), [#microservices](https://daily.dev/tags/microservices), [#agile](https://daily.dev/tags/agile)

[View this post on daily.dev](https://daily.dev/posts/why-i-m-no-longer-talking-to-architects-about-microservices-ltjl3nkaw)