You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies for deviating from the typical issue template.
I have a fundamental question about packaging all share-latex services as a single service. Under-the-hood, share-latex employs loosely coupled microservices then why is it that it is packaged as a single overleaf image? Does it not violate a recommended practice of microservice architecture to decompose the application for isolation, resilience? Or was the reason to make end-user installation easier?
Is there a way to run the microservices individually in multiple docker containers with prometheus+grafana? I want to do some load-testing where I need to see how much resources does each microservice consume under a static load?
The text was updated successfully, but these errors were encountered:
Hi,
Apologies for deviating from the typical issue template.
I have a fundamental question about packaging all share-latex services as a single service. Under-the-hood, share-latex employs loosely coupled microservices then why is it that it is packaged as a single overleaf image? Does it not violate a recommended practice of microservice architecture to decompose the application for isolation, resilience? Or was the reason to make end-user installation easier?
Is there a way to run the microservices individually in multiple docker containers with prometheus+grafana? I want to do some load-testing where I need to see how much resources does each microservice consume under a static load?
The text was updated successfully, but these errors were encountered: