DEV Community

Cover image for Product Comparison: TeamCode Pylon VS Docker Dev Environment

Posted on • Updated on

Product Comparison: TeamCode Pylon VS Docker Dev Environment

The emergence and popularization of cloud computing technology reduces the production cost of enterprises greatly. At the same time, more and more software companies started their digital innovations, exploring more efficient ways of remote development and work. For example, Microsoft released VS Code Remote in 2019, which supports remote development and ushered in a new era. According to StackOverflow's 2019 annual survey, VS Code has become the first choice for developers at that time. After that, Coder open sourced the code-server, allowing VS Code to run on any platform and access it through a browser, solving the problem of environmental inconsistency across devices, satisfying developer's needs for a more flexible, convenient, and efficient collaborative way of working. In this way, a remote development infrastructure has been created, many companies started to launch remote development tools, such as Pylon of TeamCode and Docker's Development Environments.

Analysis of User Value

For developers - Difficulties with Environment Configuration
The first step to develop a project is to build a development environment on PC.

Image description
Usually we will read the project documentation and configure the development environment according to the tutorial. However, in these seemingly most basic things that various problems may occur:

  1. The installation environment reports an error and cannot continue;
  2. The required environment conflicts with the local environment;
  3. The project was finally succeed, but could not be started;
  4. Different systems lead to installation failure. For example, some developers use Windows operating system.

Image description

All those problems always make developers frustrated. Let's have a look at how these two tools help solve issues with environment installation and configuration.

To solve those development issues, TeamCode releases Pylon, which can automatically build a scalable cloud development environment.


  1. Set up a development environment from a Git repository URL in seconds.
  2. Provide a standardized development environment.
  3. Support for mainstream IDEs and browsers, client IDE access, seamless connection with TeamCode Cloud-IDE.
  4. Support multiple languages, including Java, Python, Go, Typescript, etc.


  1. Automatically manage the cloud dev environment which can reduce the cost of R&D.
  2. All development data is stored in the cloud to enhance data security.
  3. Manage the development process in the cloud, improve data transparency and management efficiency.

Analysis of the Product Structure

The target users are developers, so it focuses on their needs, solving cumbersome issues during software development.

Scenario One: How to satisfy the demands of developers on building environment
It supports setting up a development environment from a Git repository.

Image description
Auto-testing and building the environment

Image description
You can choose VS Code or Cloud IDE to connect the environment and develop your project.

Image description

Image description

Dev Environment
It supports creating a development environment from:
1\ Git repository URL
2\ Local files
3\ Docker images

Image description
The environment will be created automatically.
Image description
Open the VS Code to access the environment.
Image description
Then you can start your development.
Image description

Scenario Two: How to satisfy the demands to preview the project before release**
Image description
You can preview the adjustments of the project via the URL, no need to go through the CI\CD process.
Image description

Dev Environment
Image description
You have to push your code through Git and implement CI\CD to preview.

Future prospects and optimization suggestions for TeamCode Pylon

I think that in addition to avoiding the cumbersome processes during software development, Pylon can also become an online preview test service, which can improve the efficiency of the whole team, and allow the product and operation team to preview code changes in time. Docker's Dev Environment still follows the traditional CI\CD path, which is relatively inefficient in this scenario.
It is recommended to be able to create a development environment locally, because if users are forced to use the cloud development environment, it means that all the development infrastructure has to move to the cloud. Compared with local development, the cost is higher, which Docker's Dev Environment is better at this point.

Discussion (0)