Hacker News - Newest: "microservices"

Microservices for the Benefits, Not the Hustle

WolfOliver — Fri, 12 Jun 2026 06:14:03 +0000

Article URL: https://kiss-and-solid.com/blog/microservices-for-the-benefits

Comments URL: https://news.ycombinator.com/item?id=48500524

Points: 1

# Comments: 0

AI versus Microservices

systems — Wed, 13 May 2026 16:52:41 +0000

Article URL: https://www.michaelnygard.com/blog/2026/05/ai-versus-microservices/

Comments URL: https://news.ycombinator.com/item?id=48124411

Points: 2

# Comments: 0

AI versus Microservices

felipehummel — Tue, 12 May 2026 18:03:18 +0000

Article URL: https://www.michaelnygard.com/blog/2026/05/ai-versus-microservices/

Comments URL: https://news.ycombinator.com/item?id=48111899

Points: 3

# Comments: 0

An agent skill for closed-loop validation on microservices

jaguar75 — Tue, 12 May 2026 16:51:26 +0000

Article URL: https://www.signadot.com/docs/integrations/coding-agents/agent-skills

Comments URL: https://news.ycombinator.com/item?id=48110865

Points: 1

# Comments: 0

AI versus Microservices

matrix — Mon, 11 May 2026 18:57:13 +0000

Article URL: https://www.michaelnygard.com/blog/2026/05/ai-versus-microservices/

Comments URL: https://news.ycombinator.com/item?id=48099175

Points: 3

# Comments: 0

What agentic AI borrowed from microservices (and made worse)

mmegger — Wed, 29 Apr 2026 18:25:18 +0000

Article URL: https://temporal.io/blog/what-agentic-ai-borrowed-from-microservices

Comments URL: https://news.ycombinator.com/item?id=47952343

Points: 1

# Comments: 0

Agents Are Microservices with a Brain

chtefi — Tue, 28 Apr 2026 16:05:41 +0000

Article URL: https://blog.dataengineerthings.org/the-microservices-playbook-for-multi-agent-systems-4d386cef62e8

Comments URL: https://news.ycombinator.com/item?id=47936341

Points: 1

# Comments: 0

Ask HN:Multi-microservices e2e tests solution

tonyxia — Wed, 15 Apr 2026 03:17:35 +0000

We're building a tool that generates E2E tests for multi microservices from Swagger specs and business logic descriptions — no traffic recording setup required. Fake data flows through all real services in your testing environment and outcomes are validated against user-confirmed expected results.

Before we launch, I'm trying to understand how teams actually solve this today.Also, a few questions for anyone dealing with this:

1. How many microservices does your team run in production?

2. Do you have true cross-service E2E tests, or mostly mocked integration tests?

3. If a tool could generate these tests from your Swagger + a plain-language description of your business flow, would that be useful enough to try?

Happy to share more about what we're building with anyone interested.

Comments URL: https://news.ycombinator.com/item?id=47774288

Points: 1

# Comments: 1

The pain of microservices can be avoided, but not with traditional databases

nathanmarz — Mon, 06 Apr 2026 16:59:44 +0000

Article URL: https://blog.redplanetlabs.com/2026/03/31/the-pain-of-microservices-can-be-avoided-but-not-with-traditional-databases/

Comments URL: https://news.ycombinator.com/item?id=47663575

Points: 6

# Comments: 0

Cell Phone Networks Are Just Microservices

wglb — Mon, 06 Apr 2026 13:20:28 +0000

Article URL: https://www.cape.co/blog/cell-phone-networks-are-just-microservices?slug=blog

Comments URL: https://news.ycombinator.com/item?id=47660553

Points: 1

# Comments: 0

Does coding with LLMs mean more microservices?

jer0me — Mon, 06 Apr 2026 02:33:21 +0000

Article URL: https://ben.page/microservices

Comments URL: https://news.ycombinator.com/item?id=47656335

Points: 63

# Comments: 61

Rethinking "2PC is not an option in Microservices"

feeblefakie — Wed, 01 Apr 2026 08:11:38 +0000

Article URL: https://medium.com/scalar-engineering/rethinking-2pc-is-not-an-option-in-microservices-a3a4e8523fcb

Comments URL: https://news.ycombinator.com/item?id=47598208

Points: 2

# Comments: 0

Distributed Tracing in Microservices: How It Works

ayoisaiah — Wed, 25 Mar 2026 13:04:42 +0000

Article URL: https://www.dash0.com/knowledge/what-is-distributed-tracing

Comments URL: https://news.ycombinator.com/item?id=47516821

Points: 1

# Comments: 0

Microservices and the First Law of Distributed Objects (2014)

pjmlp — Fri, 20 Mar 2026 15:26:24 +0000

Article URL: https://martinfowler.com/articles/distributed-objects-microservices.html

Comments URL: https://news.ycombinator.com/item?id=47455961

Points: 51

# Comments: 37

Cell Phone Networks Are Just Microservices

soopurman — Thu, 19 Mar 2026 15:41:12 +0000

Article URL: https://www.cape.co/blog/cell-phone-networks-are-just-microservices?slug=blog

Comments URL: https://news.ycombinator.com/item?id=47441315

Points: 3

# Comments: 0

Ask HN: How do you vibe code in microservices without breaking everything?

qbacode — Thu, 19 Mar 2026 14:48:30 +0000

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.

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.

How are you dealing with this? Or is everyone just praying between deploys?

Comments URL: https://news.ycombinator.com/item?id=47440460

Points: 4

# Comments: 6

Show HN: dank-py – turn existing Python agents into microservices in 2 commands

deltadarkly — Thu, 19 Mar 2026 14:00:21 +0000

Article URL: https://github.com/Delta-Darkly/dank-py

Comments URL: https://news.ycombinator.com/item?id=47439607

Points: 4

# Comments: 1

Why sharing domain data across microservices is a silent killer

davidvartanian — Sun, 15 Mar 2026 18:06:18 +0000

I spent a few years working at a company where all our microservices backed into MongoDB instances. We were constantly under top-down pressure to deliver fast, and because MongoDB is schemaless, it felt very easy to just add fields to our documents whenever we needed to expose data to another service. We eventually arrived at what we thought was a genius optimization. We wrote a background script to propagate changes from Collection A in one service to another service database. That way, the second service would not need any code modification to see the data it needed.

Every time I remember that I still feel bad for not pushing back. We created an unclear interface that coupled our domains together. The second service became dependent on the internal document structure of the first, yet it had no contract to enforce that structure. We chose that path because it was the fastest way to hit our sprint goals. We let the immediate pressure win, and in doing so, we essentially guaranteed that both maintainer teams would be locked in a fragile, entangled dance for the foreseeable future.

I have since learned that sharing domain data across boundaries is a recipe for disaster. It is a classic example of prioritizing speed in the present while ignoring the mounting cost of coupling. The better approach should've been to respect domain boundaries and only connect them using a unique immutable identifier instead of sharing stateful objects or duplicating documents. By passing an ID, you maintain the independence of each service so they are free to evolve at their own pace, as long as they don't break the interfaces.

Comments URL: https://news.ycombinator.com/item?id=47390041

Points: 1

# Comments: 0

Microservices: Shackles on Your Feet

birdculture — Sat, 14 Mar 2026 20:28:34 +0000

Article URL: https://howtocenterdiv.com/beyond-the-div/microservices-shackles-on-your-feet

Comments URL: https://news.ycombinator.com/item?id=47380832

Points: 8

# Comments: 1

From Monolith to Microservices: The Redistribution of Complexity

ibobev — Thu, 12 Mar 2026 14:41:20 +0000

Article URL: https://www.ddhigh.com/en/2026/03/12/complexity-redistribution-from-monolith-to-microservices/

Comments URL: https://news.ycombinator.com/item?id=47351242

Points: 1

# Comments: 0