Setting up a development environment
Setting up a development environment mimicking a production one is highly recommended to ensure faster feedback during the development stages, as well as to fix any anomalies in code before promoting it to a production setup. Although running services in a container increases the flexibility of rolling back if issues are detected after deployment into production, a best practice is to act proactively by running service containers in an isolated environment through different deployment and testing stages. Upon successful deployment in the test environment, services’ containers will be promoted and tagged as production-ready for deployment.
Depending on how many physical machines will be invested in your development environments, the DevSecOps team will require an isolated environment for each member to run tests, before committing their changes to a main development branch that targets deployment in the development environment.
