Multiple containers, same application, behind a caddy reverse-proxy routing to container 1 or 2 in function of the path

I think your questions are more-or-less covered by this article:

I’d recommend that you use subdomains for each “feature”, so like feature1.admin.example.com or something similar.

That said, I’d say that microservice architectures… are a dangerous idea. You end up doing a lot of the same things in each one. Performance can suffer significantly because of added overhead.

Monolithic apps are fine.

1 Like