The failover scenario of requests coming through the client is handled by the delegated repo using Ocelot.
-
Updated
Jun 11, 2024 - C#
The failover scenario of requests coming through the client is handled by the delegated repo using Ocelot.
Microservice : A project made for understanding the mircoservice architecture. Made with .net framework, using Docker, RabbitMQ, Ocelot, Eureka.
NikeShop is an open source e-commerce site based on enterprise-grade microservice architecture. Tech Stack- .Net Core, EF Core, Ocelot API Gateway, RabbitMQ, .NET Identity, SQL Server, JWT Tokens. Project Will Be Live Soon
Microservice, RabbitMQ, Azure Service Bus, Domain-Driven-Design, MSSQL, Redis, Ocelot (ApiGateway)
Microservice application made as a semester work. My main and favorite project.
This repository contains simple samples demonstrating the use of Ocelot to build an API Gateway in .NET. Explore the provided examples to learn how to leverage Ocelot for routing and aggregation in your microservices architecture.
Securing .NET 8 microservices with using OAuth2.0 and OpenID Connect implemented, standalone Identity Server 4; backing with Ocelot API Gateway.
This minimal API allows handling JSON requests with any capitalization and provides JSON responses
Microservice with docker(docker compose)
esport - sport organisations management system
Huge educational project, with microservices for online game. Check the README to see the technologies used.
This repository includes given homeworks in Inveon Fullstack Bootcamp.
Inveon Bootcamp - Microservice Architecture Example
ASP.NET Microservices Shopping App with Blazor and Razor Pages as two Client apps using Ocelot API, RabbitMQ, Docker, Redis, MongoDB, PostgreSQL, SQL Server, Dapper, Entity Framework
Simple implementation of ocelot api gateway with two microservices.
Ocelot.Provider.SqlServer enables dynamic route management by storing Ocelot routes in a SQL Server database, eliminating JSON files. Designed for ASP.NET, it fully supports .NET 6.0.
Ocelot is an open-source API Gateway for the .NET/Core platform that allows us to unify multiple microservices under a single domain, providing a clean separation between the client and microservices. It acts as a gateway for incoming requests from the client and forwards them to the appropriate microservices.
Add a description, image, and links to the ocelot-api-gateway topic page so that developers can more easily learn about it.
To associate your repository with the ocelot-api-gateway topic, visit your repo's landing page and select "manage topics."