-
Notifications
You must be signed in to change notification settings - Fork 6k
Closed
Labels
Description
Help us make content visible
- dotnet-architecture
- Previous docs: https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/implement-api-gateways-with-ocelot.
Describe the new article
- In eshopOnContainers, API Gateway is migrated from Ocelot to Envoy, so documentation needs to be updated.
- Location: https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/implement-api-gateways-with-ocelot.
- The reference microservice application [eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainers) has implemented Envoy as API Gateway, this has replaced the previous implementation Ocelot, This document will cover how to implement API Gateways with Envoy and how to use Envoy in a container-based environment.
- Create an outline for the new article. We'll help review the outline and approve it before anyone writes the article.:
- Architect and design your API Gateways
- Implementing your API Gateways with Envoy
1. Main Components
2. Set up Envoy
3. Implement API Gateways with Envoy
4. Describe envoy.yaml configuration
5. How Envoy Helps in this application
- Using Kubernetes Ingress plus Envoy API Gateways
[Edit to add doc details]
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 10ce8eaa-b3ff-9b69-fea1-131eed36b9ec
- Version Independent ID: 771d9f72-b506-79ef-5398-030c1705ee9a
- Content: Implementing API Gateways with Ocelot
- Content Source: docs/architecture/microservices/multi-container-microservice-net-applications/implement-api-gateways-with-ocelot.md
- Product: dotnet-architecture
- Technology: microservices
- GitHub Login: @nishanil
- Microsoft Alias: nanil