you could have them in the same project. You would just have to create subdomains for each of the service. so for instance your backend would be api.yourapp.com then the store would be yourapp.com. the admin would be admin.yourapp.com

Typically, in the current microservice architecture, it is usually done by directly accessing a single front-end service, which is routed by the front-end and then distributed to the designated microservice backend through the Gateway.

However, for the scenario you described, I suggest that you can deploy another service to customize the reverse proxy service, such as the nginx container.

And bind your main domain name for this reverse proxy service. All network entrances and exits will be forwarded through here.

Hope it can be of some help to you.

i assume they are 3 components that make up one app, right?

do they live in separate git repos?

i assume your Vendor admin front end, and a customer facing storefront need to talk to the Medusa backend

if my assumptions are correct you can create three services in the same project from the 3 repos and connect the frontends to the backend by using the internal url that doesn't incur egress charges.

Then via a Generated domain you can access the customer storefront to see that it is working.

As a next step you need to set up a Custom Domain for your storefront www.myshop.com and then set up a subdomain admin.myshop.com for the admin