Using .NET Aspire with Azure API Management in an Azure Landing Zones architecture? #1096
-
|
Hi Aspire team and community TL;DR I’m trying to understand whether Aspire fits into our architecture, or if our use case is intentionally out of scope — and I’d appreciate a sanity check. Our current setup (simplified)We’re following Microsoft Azure Landing Zones (CAF) guidance:
Even APIs that are only consumed by their “own” frontend are still registered in APIM to maintain consistent governance. What we’re trying to evaluateWe see the value of Aspire for:
However, we struggle to see how Aspire fits when:
We’ve also seen discussions (e.g. #59) indicating that native APIM integration is not planned, which is completely understandable. The core questionGiven an APIM-first Azure Landing Zones architecture:
I want to make sure we’re not trying to force Aspire into a space it was never designed for — and if the answer is “this is intentionally out of scope”, that’s perfectly fine. Thanks for building Aspire and for any guidance you can share! Note: I had some AI help drafting this post due to dyslexia — thank you for your understanding. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
This is probably the wrong place to ask, you'd be better asking in the dotnet/aspire or on the Aspire Discord |
Beta Was this translation helpful? Give feedback.
This is probably the wrong place to ask, you'd be better asking in the dotnet/aspire or on the Aspire Discord