[Question] Using Ocelot Configuration.Json files in multiple projects for BFF framework

[aravindkoniki]

Hello,

I have started designing API gateway using OCELOT, as BFF framework following Microservices architecture.

Here my question is, in that project the configuration.json files are placed in different projects, and thoose projects are not installed with OCELOT framework, there is one project called OCELOTAPIGW as base for other gateways,

i'm not very much clear about the architecture, how this configuration files are merging and ocelot gateway is acting as base for all other projects, please see the below shot for the project structure i explained

[CESARDELATORRE]

We're re-using exactly the same Docker image for the three API-Gateways, that's why each folder just has its specific configuration.
If you take a look to the docker-compose.yml file you'll notice that.I'll document this in the eBook in the upcoming weeks.
Thanks for the question.

[aravindkoniki]

Thanks, I have noticed that. How do the routing happens here.

Example, if a request from client will reach to MobileShoppingAggregator first? if yes, then will it pass through the OCELOTAPIGW to communicate with the other microservices based on the configuration ?

How do it automatically redirects to OCELOT APIGATEWAY Configurations ? can you help me on this

[eiximenis]

Hi.
> a request from client will reach to MobileShoppingAggregator first?
No, a request from client always go through Ocelot ApiGateway first. Then ApiGateway redirects the request to Aggregator. Calls from aggregator to any other service are direct.

From a client perspective only the Api Gateways need to be reachable (in a prod env only Api Gateways would need a ingress entry). Aggregators and microservices are both considered internal.

[aravindkoniki]

Thanks, I'm clear little bit, still I have some couple of questions on the communication between aggregators, micro services and gateway, will wait for your documentation.

[CESARDELATORRE]

Closing this, for now. Can be re-open in needed.