Skip to content

Update microservices ebook - Implement API Gateways with Envoy #29106

@erjain

Description

@erjain

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions