How fscdesarrollo/learning-internal-gateway works
Project type and purpose
• Full-stack proof-of-concept for internal gateway communication
• Uses .NET Core 8 microservice (Transactions.API), an API gateway (Learning.InternalGateway.Gateway with Ocelot), a Razor-Pages web front end, and Keycloak for authentication
File structure
• Top-level solution (Learning.InternalGateway.sln) and docker-compose.yml for spin-up
• “src/…Gateway” – the Ocelot API gateway project, with ocelot.json routing config and shared middleware (AuthorizationHandler)
• “src/…Transactions.API” – a backend microservice exposing transaction endpoints
• “src/…Web” – Razor-Pages UI that calls the gateway via ITransactionApi service, serves static assets under wwwroot
• “src/…Shared” – common code (DTOs, logger config, authorization handlers) reused by gateway and API
README for additional insights
• PoC uses .NET Core 8, Ocelot, Keycloak
• No explicit database project—assume Transactions.API will connect to a data store (can be mocked or added later)
Elements
• Clear labels on each component (e.g., “Learning.InternalGateway.Gateway (Ocelot)”)
– Blue for front-end/UI
– Green for API Gateway
– Orange for microservices
– Purple for external/auth (Keycloak)
– Gray for data store