I'm trying to figure out the best Azure service to use for creating a facade or gateway API to hide two backends that expose REST APIs. I need this facade to manage routing, apply inbound and outbound rules, perform authentication (preferably with custom logic in .NET), and maintain WebSocket connections since the client is a web application that needs to interact with both APIs. Would Azure API Management work for this, or would I be better off developing my own solution with something like YARP? Any insights would be greatly appreciated! Cheers!
3 Answers
You can also consider using Azure Application Gateway with a Web Application Firewall (WAF). This setup lets you expose the API under your own domain and build custom rules for traffic management, but just double-check if it supports the custom authentication you need.
Azure API Management seems like a strong choice for what you're looking to do. It's specifically designed for managing APIs, including routing and authentication, and would work well as a facade. However, keep in mind it typically suits scenarios where the API is part of a SaaS offering.
That makes sense! I was just wondering if there are alternatives that might fit better if it's not a SaaS situation. Thanks for clarifying!
Both Azure API Management and YARP would work depending on your preferences and budget. If you're leaning towards .NET, YARP is a solid choice and can be lighter on costs compared to Azure's API Management service.
Good point! Can you run custom authentication easily on Azure Application Gateway with WAF?