> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/fr/concepts/intermediate-concepts/topology.md). # Topologie La topologie de Devolutions Server décrit comment le serveur web, la base de données et les gateways se connectent, en couvrant les modèles de déploiement tout-en-un, séparé et DMZ. La topologie dans un déploiement de Devolutions Server décrit comment le serveur web, la base de données, les gateways et les clients sont disposés et connectés. Les modèles courants comprennent les installations tout-en-un, les serveurs web et de base de données séparés, ainsi que les conceptions qui placent les composants de Devolutions Gateway dans une zone démilitarisée pour un accès distant sécurisé. Comprendre votre topologie facilite la planification de la capacité, le dépannage et les revues de sécurité. La documenter en parallèle des coffres et utiliser une nomenclature cohérente pour les hôtes et les services permet aux nouveaux administrateurs de mieux comprendre comment le trafic circule dans l'environnement. #### Sujets connexes * [Topologies](/server/fr/overview-of-devolutions-server/topologies.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/server/fr/concepts/intermediate-concepts/topology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.