.NET Aspire sounds cool. But do I aspire to use it?

No😉

Everyone's talking about it. But… I still don’t get what problem it's solving.

✅ My apps run fine without it. ✅ My dev life isn’t exactly full of orchestration pain. ✅ The benefits? Mostly marketing smoke and vague promises.

Also…

❌ It’s brand new (read: immature). ❌ It's Microsoft. These things tend to… disappear... ❌And Aspire pulls you deeper into the MS glue trap

I try to avoid that.

Even Docker Compose is already a bit too much glue for me sometimes.

Keep it stupid simple, remember?

Let’s be real: Most apps don’t need a microservices control tower. They just need to work. Be stable. Be simple.

So for now, I'm skipping Aspire. I'll watch from a distance while others play with the glitter.

What’s your take? Do you think .NET Aspire is the next big thing—or just another hype train?

One email every Sunday

The week's blog post, straight to your inbox. No spam. No fluff.

I respect your inbox. Unsubscribe any time.

AI does not need MCP to call an API. It can make HTTP requests directly. Read the documentation. Handle authentication. Parse the response. No...

The skill that gets automated first is the one that looks most like translation work. Building flows in Power Automate is translation work: take a...

Connectors were always training wheels. They solved one specific problem: non-developers could not write API calls. So Microsoft built 400+...