Module Configuration for 1C-Bitrix Enterprise Edition

The "Enterprise" edition is the top tier of the 1C-Bitrix product line. This is where tools appear that are only needed under serious load and complex infrastructure: clustering, database replication, web cluster. A misconfiguration in "Enterprise" is more costly than a mistake in "Start" — the consequences affect the entire cluster.

Module Configuration for 1C-Bitrix Enterprise Edition

Key Differences of Enterprise

In addition to everything in "Business," "Enterprise" adds:

• Web cluster (cluster) — multiple frontend servers, load balancing
• Multi-session without sticky sessions — sessions in memcached/Redis, accessible to all cluster nodes
• DB replication — master for writes, slave for reads
• CDN integration — static assets served via CDN
• Extended permissions management — more granular access control to sections and modules
• Personalization — content display based on user behavior history

Web Cluster Configuration

The cluster module is configured via Settings → Web Cluster. Main tasks:

Session storage. By default, Bitrix stores sessions on the filesystem — this doesn't work in a cluster (each request can hit a different node). Switch to memcached or Redis:

• Settings → Web Cluster → Sessions
• Specify the memcached/Redis server address
• Verify that all cluster nodes can see the same session server

Component cache. Similarly — switch managed_cache to memcached. Settings in /bitrix/.settings.php:

'cache' => [
    'value' => [
        'type' => 'memcache',
        'memcache' => ['host' => '127.0.0.1', 'port' => 11211],
    ],
],

File synchronization. When files change (image upload, template update) the filesystem needs to be synchronized between nodes. Solutions: NFS share, GlusterFS, S3-compatible storage (MinIO or AWS S3).

Database Replication Configuration

In Settings → Web Cluster → DB Replication. Add MySQL/PostgreSQL slave servers. Bitrix automatically routes SELECT queries to the slave and INSERT/UPDATE/DELETE to the master.

Critically important after setup: verify that transactions work correctly — operations inside a transaction must go strictly to the master, even if they include SELECT statements. Bitrix handles this, but custom code with direct database queries does not.

CDN and Static Assets

Settings → Web Cluster → Resources. Specify the CDN domain (e.g., static.example.com). Bitrix replaces paths to static assets in HTML with the CDN domain. Requirements: the CDN must have access to the origin server (pull model) or files are synchronized directly (push model).

For redundancy and performance — enable gzip compression at the web server level and configure Cache-Control headers for static assets.

Personalization

The personalization module works on visitor profiles: browsing history, purchases, geolocation. Configuration in Marketing → Personalization:

• Create visitor segments (e.g., "viewed category X," "from Moscow," "purchased Y")
• Configure content display rules: for segment A show block B
• Connect personalization components in the site template

Case Study: Cluster for a Large Retailer

A retailer with peak load of 500+ RPS during promotions. Architecture: 3 frontend nodes behind an Nginx load balancer, master + 2 slave PostgreSQL, Redis for sessions and cache, S3 for files, CDN for static assets. Setup: 2 weeks. Most of the time was spent on file synchronization between nodes and debugging transactions after enabling replication (several custom modules were writing directly to the slave connection).

Timelines