In Cofinity-X systems, it is crucial to ensure that your data behaves reliably and efficiently for your partners. This is where the distinction between production and pre-production environments becomes essential. For Cofinity-X systems, which manage complex data workflows and integrates with multiple systems, maintaining well-defined environments is vital to your success.
But what exactly separates these two environments, and why is it important to have a pre-production environment in place?
In this article, we will explore the key differences between production and pre-production environments within Cofinity-X systems, discussing their unique purposes, configurations, and roles in a typical software development lifecycle.
Production Environment
The production environment is the live system where you and your partners interact with Cofinity-X systems, making it crucial for maintaining stability, reliability, and performance. Any issues here can directly impact your data and your business operations.
Pre-Production Environment
In contrast, the pre-production environment is the staging area used for testing, quality assurance, and final validation. It mirrors the production environment’s configurations but operates in isolation, allowing you to simulate real-world scenarios, identify bugs, and fine-tune performance and data without risking disruptions to live services. This separation minimizes the risk of errors reaching the production environment.
How to differentiate between Production Environment and Pre-Production Environment?
All data for pre-production are easy to recognize, because only these contain URLs or paths such as:
beta
preprod
This also applies to your Dataspace OS working environment.
Example URLs
An URL for pre-production
did:web:portal-backend.beta.cofinity-x.com:api:administration:staticdata:did:BPNL0000000XXXXX
The same URL for production, replacing "beta" part with "svc"
did:web:portal-backend.svc.cofinity-x.com:api:administration:staticdata:did:BPNL0000000XXXXX
An URL for Dataspace OS pre-production
https://frontend.dataspaceos.preprod.cofinity-x.com/componentsThe same URL for Dataspace OS production, replacing "preprod" part with "svc"
https://frontend.dataspaceos.svc.cofinity-x.com/components
Best Practices for Dataspace OS
Before making any changes in your production environment, specify the desired behavior and the required changes.
Make sure to log out the Dataspace OS production environment. Only work within Dataspace OS pre-production environment.
Create meaningful data and tests in your pre-production environment in accordance with your specifications.
Test all data, connections, services and operations in your pre-production environment.
Finally, when all tests have been successful you can start to implement the specifications in your production environment.
Make sure to adjust all URLs for the production environment.