Remote Development Environments (RDEs)
Problem
Developers waste a lot of time setting up the local development environment and regularly struggle with compatibility problems. In fact, regular troubleshooting is one of the main problems developers face. It eats up time, resources and reduces productivity.
Solution
Remote Development Environments (RDEs) are standardised remote environments that are immediately available without setup time. Developers have immediate access to all the tools they need for their work and receive the computing power they need for resource-intensive tasks.
The problem
- The initial setup of the local development environment takes time.
- Onboarding software developers or changing devices is difficult.
Differences in local development environments affect productivity. - There is no standardized support, a lot of time is spent on troubleshooting.
- Powerful and expensive equipment is needed to use applications locally (your own software, testing tools, etc.).
- Productivity losses because of waiting for tests, builds, etc. Change of Version / branch is time consuming, because all dependencies have to be set up again.
- Source code is stored locally and insecurely.
The solution
- Remote development environments that are centrally managed by the DevOps team and used by software developers as a service.
- Standardised environments that are available with one click: Run complex applications such as large monoliths and non-containerised software in RDEs and deploy them immediately.
- Continue to use all your individual tools: Integration via a mounted file share with all sources for your favourite local editors / IDEs or via SSH for web / remote IDEs.
- Build of not yet committed intermediate states, reuse of already existing local build tools (e.g. code not minimised) and comfortable inspection of logs.
- Extensive automation and integration functionality: Automate additional processes as needed with Cloudomation.
How it works
Self-service frontend: Select, create and remove RDEs via the self-service frontend and get an overview of running RDEs
Configuration frontend: Determine which remote development environments are available via the self-service frontend. Configuration of the data model and use of configuration templates possible.
Automation front-end: Define how remote development environments are created. Integrate tools and use existing automation workflows or processes implemented by other automation tools.
The result
Comprehensive standardization:
- Central management of development environments.
- The same system for all: Automated deployment exactly according to company requirements – at the push of a button.
- Use the same tools for development, production, testing and deployment.
Massive time savings:
- No setup time during onboarding and daily work.
- Time for troubleshooting the development environment is reduced to zero.
- Parallel work on different branches / versions: with a simple change of RDE.
Developer friendly & secure work:
- No hardware limitation: Computationally intensive processes are carried out in the RDE. Theoretically, development can even be done on a tablet.
- Software development with and without internet connection.
- Air-gapped RDEs for security of source code and data: Can be set up so that source code never ends up locally on the developer’s computer.
