Fabric Environments Security
Fabric benefits from being deployed to the following environments for the respective phases of a project's lifecycle, from inception to delivery and maintenance.
Table of Contents
Development Environment
This environment should contain:
- Fabric Server for each developer.
- Windows for installing and running the Fabric Studio.
- SVN / GIT for version control.
Access to this server and SVN / GIT should be limited to the relevant developers.
QA Environment
This environment should be isolated from the Development environment and should contain the following components:
- Fabric servers cluster, minimum 3 for Testing
- Windows Terminal Server, for installing and running Fabric Studio.
- Access to Fabric WS (API) via the load balancer (LB).
- Access to SVN/GIT for version control, limited to relevant users.
- Source databases, including data that should have the same structure as in the Production environment.
Note that all connection methods and protocols must be of the same type as those defined in the Production environment. All access to the above-described servers should be limited to the QA team members only.
Pre-Production Environment
This environment should be isolated from the Development and QA environments and should be identical to the Production environment:
- Fabric servers cluster, identical as possible to the Production environment (minimum 3 on each DC)
- Windows Terminal Server for installing and running the Fabric Studio. Access to this server should be limited to the relevant Admin team only.
- Access to the Fabric WS (API) via the load balancer (LB).
- Access to SVN/GIT for version control, limited to relevant users.
- Source databases, including data that should have the same structure as in the Production environment.
Note that:
- All connection methods and protocols must be identical to those defined in the Production environment.
- All access to the servers described above should be limited to the QA team members only.
- The connection method and protocol must match those used in the Production environment.
- This environment should be sufficiently strong to be able to run load testing.
Production Environment
This environment should be isolated from the Development and QA environments and should be identical to the Pre-Production environment:
- Fabric server cluster, according to the production sizing definitions.
- Windows Terminal Server, for installing and running Fabric Studio. Access to this server should be limited to the relevant Admin team only.
- Access to the Fabric WS (API) via the load balancer (LB).
- Access to SVN/GIT for version control should be limited to the relevant users.
Fabric Environments Security
Fabric benefits from being deployed to the following environments for the respective phases of a project's lifecycle, from inception to delivery and maintenance.
Table of Contents
Development Environment
This environment should contain:
- Fabric Server for each developer.
- Windows for installing and running the Fabric Studio.
- SVN / GIT for version control.
Access to this server and SVN / GIT should be limited to the relevant developers.
QA Environment
This environment should be isolated from the Development environment and should contain the following components:
- Fabric servers cluster, minimum 3 for Testing
- Windows Terminal Server, for installing and running Fabric Studio.
- Access to Fabric WS (API) via the load balancer (LB).
- Access to SVN/GIT for version control, limited to relevant users.
- Source databases, including data that should have the same structure as in the Production environment.
Note that all connection methods and protocols must be of the same type as those defined in the Production environment. All access to the above-described servers should be limited to the QA team members only.
Pre-Production Environment
This environment should be isolated from the Development and QA environments and should be identical to the Production environment:
- Fabric servers cluster, identical as possible to the Production environment (minimum 3 on each DC)
- Windows Terminal Server for installing and running the Fabric Studio. Access to this server should be limited to the relevant Admin team only.
- Access to the Fabric WS (API) via the load balancer (LB).
- Access to SVN/GIT for version control, limited to relevant users.
- Source databases, including data that should have the same structure as in the Production environment.
Note that:
- All connection methods and protocols must be identical to those defined in the Production environment.
- All access to the servers described above should be limited to the QA team members only.
- The connection method and protocol must match those used in the Production environment.
- This environment should be sufficiently strong to be able to run load testing.
Production Environment
This environment should be isolated from the Development and QA environments and should be identical to the Pre-Production environment:
- Fabric server cluster, according to the production sizing definitions.
- Windows Terminal Server, for installing and running Fabric Studio. Access to this server should be limited to the relevant Admin team only.
- Access to the Fabric WS (API) via the load balancer (LB).
- Access to SVN/GIT for version control should be limited to the relevant users.
