提问 HN：在微服务架构中，如何编写代码才能保持良好状态，同时避免全面崩溃？
4 分•作者: qbacode•4 天前
上周，我们用 AI 助手重命名了一个服务中的字段。结果导致另外三个服务在生产环境中崩溃。代码审查时没人发现这个问题，因为这些依赖关系不在代码里，而是在大家脑子里。<p>我们公司正推动我们用更少的开发人员交付更多产品，大家都用 Claude Code。它在单个服务内的开发速度方面表现出色。但对于微服务呢？这就像把电锯交给一个看不见墙的人。AI 的行动速度远超团队追踪依赖关系的能力。<p>你们是怎么处理这个问题的？还是大家每次部署前都在祈祷？
查看原文
We had an AI agent rename a field in one service last week. Three other services broke in production. Nobody caught it in review because the dependencies aren't in the code, they're in someone's head.<p>My company is pushing us to ship more with fewer devs, we all use Claude Code. And it's amazing for velocity within a single service. But microservices? It's like giving a chainsaw to someone who can't see the walls. AI moves way faster than your team's ability to trace what depends on what.<p>How are you dealing with this? Or is everyone just praying between deploys?