Platform.sh Enterprise cluster specifications

Architecture

Platform.sh Enterprise clusters are launched into a Triple Redundant configuration consisting of 3 virtual machines (VMs). This is an N+1 configuration that is sized to withstand the total loss of any one of the 3 members of the cluster without incurring any downtime. Each instance hosts the entire application stack, allowing this architecture superior fault tolerance to traditional N-Tier installations. Moreover, the Cores assigned to production are solely for production.

Cloud resources (per instance)
AWS Azure Azure DE
Orange
vCPUs
Image RAM Image RAM Image RAM Image RAM
PE6
2 c3.large 3.75 D2_v2 7 D2_v2 7 c2.large 4
PE12
4 c3.xlarge 7.5 D3v2 14 D3v2 14 c2.xlarge 8
PE24
8 c3.2xlarge 15 D4v2 28 D4v2 28 c2.2xlarge 16
PE48
16 c3.4xlarge 30 D5v2 56 D5v2 56 c1.4xlarge 64
PE96
32 c3.8xlarge 60 D32v3 128 D32v3 128 c1.8xlarge 64
PE192
64 x1.16xlarge 128 D64 256
PE384
128 x1.32xlarge 1349 D64 * 6
256

The infrastructure host image can also be altered based on your project requirements if needed. The cost implications of such a change can be discussed with your sales representative.

Storage

Each enterprise cluster comes with 50GB of storage per environment by default. This storage is intended for customer data - databases, search indexes, user uploaded files, etc. - and can be subdivided in any way that the customer wishes. 50GB is only the default amount; more storage can be added easily as a line item in the contract and can be added at anytime that the project requires: at contract renewal or at any point in the term.

Default storage is based on the default SSD block-storage offering for each cloud. Extra provisioned IOPS can be discussed with your sales representative.

Compatible services

Service Versions
PHP 5.6, 7.0, 7.1 (ZTS)
NodeJS 9.8
MariaDB 10.0 Galera, 10.1 Galera
RabbitMQ 3.6
Solr 4.10, 6.3
ElasticSearch 1.7, 2.4, 5.2
Redis 3.2
Memcached 1.4

Your application will be able to connect to each service by referencing the exact same environment variables as on Platform.sh Professional. While the configuration of the service will be performed by our team, the application configuration is the same and your code should be the same. See the Platform.sh Professional documentation for service-specific details.

Configuration & change management

Some configuration parameters for Enterprise clusters are not able to be managed via the YAML configuration files, and for those parameters you will need to open a support ticket to have the change applied. Further, the .platform/routes.yaml and .platform/services.yaml files do not automatically apply. Any existing service upgrades or new service additions will require a support ticket.

Specifically:

  • Cron commands
  • Worker instances
  • Service versions and configuration (everything in .platform/services.yaml)
  • Route, domain, and redirect configuration (everything in .platform/routes.yaml)
  • Application container version
  • Additional PHP extensions
  • Web server configuration (the web.locations section of .platform.app.yaml)

results matching ""

    No results matching ""