It is the simplest but basic form of a remote development setup. The server only allows inbound SSH requests on port 22. The experiment is conducted with a one-hop client/server setup, where the Client (my laptop) has direct access to the Server (a Virtual Machine hosted on Tencent Cloud). Server (“Remote host”) is a Linux server where the IDE backend runs.Client (“Local machine”) is the developer’s PC where JetBrains (Thin) Client runs.Here is a quick summary of the terminologies of JetBrains remote development: Please note that many conclusions are just based on logs and network packet capturing, and there could be mistakes. In this post, I will try to answer the questions from an end-user perspective by watching the process tree and monitoring the traffic between different components. The official document explained in detail both the user guide and some security concerns.

Is the network traffic routed to some relay? How should I configure the network policy if I’m hosting my remote servers in some enterprise environment?.How are different components launched and connected with each other in such a distributed way?.The split of the monolithic IDE architecture raises a couple of interesting questions: There is an official diagram introducing the architecture and definitions relating to JetBrains’ remote development. There are also numerous plugins built for customized in-house remote workspace orchestration. JetBrains Gateway is getting more and more popular, even though still in beta release, it has first-party providers like Gitpod, JetBrains Space, Google Cloud Workstations, and GitHub Codespaces.

Download jetbrains space docker