We at 10+ strongly believe that whenever possible we follow best practices and industry standards when it comes to system architecture and the development of digital solutions.
Development, staging and production
instances It is common practice to operate several instances of a system. To do this, we use a development instance in which the work of our programmers is implemented and tested in a first step.
The adjustments are then copied to a so-called staging instance. This system is almost a copy of the production instance and is used to extensively test innovations and adjustments in an environment that comes as close as possible to the actual website.
If all tests could be successfully completed, manually and partly automatically, the adaptations and further developments are transferred to the production instance (live instance), where they are then accessible on the Internet.
Deployment (rollout) process
The deployment process contains the individual steps in order to import one or more adjustments to the productive website. Such an adjustment can be a new feature, a bug fix, a configuration adjustment, a security update or something similar.
A typical deployment should be quick , serve a specific purpose, and not have any unintended side effects (regression). To achieve this, we rely on the following strategies: source code management with Git, development, staging and production instances, as well as quality assurance methods such as automated tests.
An example of such a deployment looks like the following:
- A new feature is desired
- The feature is designed and developed
- The feature is imported into the staging instance
- The feature is tested by the customer until it meets all requirements
- The automated tests are run at ensure that all other functionalities continue to run correctly
- The feature is imported into the production instance (live website)