Architecture Decision Context
Before using DataForge, customers must make a decision whether the DataForge deployment should be a standard or private enterprise architecture. This decision is not easily reversed and requires a complete tear-down of the existing environment and redeploying a new environment if a switch is needed after the initial deployment.
DataForge recommends the Standard deployment for most customers as it allows DataForge to manage the platform infrastructure and resources, removing the overhead from the client infrastructure team. For customers who are under strict compliance and regulation, the Private Enterprise deployment deploys all resources in the customer-managed VPC to be managed and monitored by the customer.
Below are comparisons of Standard vs. Private Enterprise Architecture for both AWS and Microsoft Azure hosted environments. If more clarity is needed, please engage the DataForge Support team through a support request.
Standard Deployment
The standard deployment follows a traditional software as a service architecture where DataForge hosts the platform infastructure and services. The data storage and cloud computing is hosted and managed in the customer-managed VPC.
Private Enterprise Deployment
The Private Enterprise deployment utilizes the same components but all infrastructure resources are deployed in the customer-managed VPC.
Updated