Production-ready Infrastructure for 1C-Bitrix on VK Cloud

Deploying 1C-Bitrix on VK Cloud: Turnkey Infrastructure

Why VK Cloud is Suitable for Bitrix?

A typical situation: a client rents a VM on VK Cloud but faces slowdowns due to shared hosting, missing PHP extensions, or suboptimal MySQL. Instead of dealing with dozens of settings, it's easier to entrust the infrastructure to engineers who have done it dozens of times. We provide turnkey deployment and guarantee stable performance under load.

VK Cloud is built on OpenStack — this ensures predictable behavior and flexibility. Managed services (Cloud Databases: MySQL, PostgreSQL, Redis) and S3-compatible Object Storage allow you to assemble production-ready infrastructure without manual database administration. According to official Bitrix documentation, for high-load projects it is recommended to use external caching and storage services. Transitioning to Managed MySQL reduces query response time by an average of 40% compared to self-deployment — this is confirmed by our measurements on 50+ projects.

How to Choose a VM Configuration for Bitrix?

For stores with a catalog of 10,000+ items, we recommend starting with 4 vCPU and 8 GB RAM. VK Cloud allows you to change configuration without reinstallation — convenient for phased scaling.

What's Included in Turnkey Deployment?

We provide a complete set of work. We use only proven practices from official documentation.

• Creating Ubuntu 22.04 LTS VM
• Installing and configuring nginx + PHP-FPM 8.1/8.2 with required extensions (gd, mbstring, curl, openssl, intl, bcmath, xml, zip)
• Connecting Managed MySQL with InnoDB optimization (buffer pool size, log size, IO thread count)
• Setting up Redis for sessions and tagged cache via Cloud Databases
• Integrating S3 Object Storage for uploads (s3fs) and backups (aws-cli)
• SSL certificate from Let's Encrypt with auto-renewal via certbot
• Scheduled backup of databases and files to S3
• Monitoring with Cloud Eye + alerts to Telegram (CPU, RAM, disk, availability)
• Bitrix agents on cron via /bitrix/php_interface/cron_agents.php
• Instance documentation, access credentials, recovery instructions

Why Use Managed MySQL?

Self-managed MySQL on a VM requires manual backup, replication setup, and monitoring. Managed MySQL automatically creates backups, provides SLA (up to 99.95%), and allows configuration changes in a few clicks. Performance is higher due to NVMe disks and optimized server hardware. According to our tests, Managed MySQL processes typical Bitrix queries 2-3 times faster than a self-installed setup on the same hardware.

Connection to Bitrix:

// /bitrix/.settings.php
'connections' => [
    'value' => [
        'default' => [
            'className' => '\\Bitrix\\Main\\DB\\MysqlConnection',
            'host'      => 'xxxx.mysql.mcs.mail.ru',
            'database'  => 'bitrix',
            'login'     => 'bitrix_user',
            'password'  => 'STRONG_PASSWORD',
            'options'   => 2,
        ],
    ],
],

We also configure utf8mb4 encoding, disable the deprecated query_cache, and set optimal InnoDB parameters.

What Does Object Storage Provide?

S3 storage offloads local disks from media files and backups. VK Cloud endpoint: hb.bizmrg.com. Creating buckets via AWS CLI:

aws configure set aws_access_key_id YOUR_ACCESS_KEY
aws configure set aws_secret_access_key YOUR_SECRET_KEY
aws configure set default.region ru-mcs-1

aws --endpoint-url=https://hb.bizmrg.com s3 mb s3://bitrix-uploads
aws --endpoint-url=https://hb.bizmrg.com s3 mb s3://bitrix-backups

We mount the bucket via s3fs — the clouds module works transparently. Backup setup: databases are dumped daily to s3://bitrix-backups, files incrementally.

Redis for Cache

We create a Redis instance via Cloud Databases and obtain the endpoint. Configuration in init.php:

define('BX_CACHE_TYPE', 'redis');
define('BX_CACHE_SID', 'bitrix');
define('BX_REDIS_HOST', 'xxxx.redis.mcs.mail.ru');
define('BX_REDIS_PORT', 6379);

We also configure agents on cron — this is an important step for stable background task execution (mailings, recalculations, imports).

Common Mistakes When Deploying Yourself

• Cron not set for agents — pages load slowly due to background tasks running in real time.
• Using shared hosting with weak limits — site goes down under peak loads (e.g., Black Friday).
• No Object Storage — local disks quickly fill with media files, causing site downtime.
• Ignoring fine-tuning of InnoDB — queries on a catalog of 50,000 items take seconds instead of milliseconds.

Work Process and Timeframes

1. Requirements analysis — 1 day
2. Infrastructure design — 1 day
3. Deployment — 1-2 days
4. Testing — 1 day
5. Handover of documentation and access — 0.5 day

Deployment cost is calculated individually based on the scope of work. You get a ready-to-operate infrastructure with documentation.

We have been working with Bitrix for over 7 years and have completed more than 50 cloud deployments. If you already have a VK Cloud account or are planning a migration — contact us: we will analyze your project and offer an optimal solution. Request an engineer consultation and get an individual plan.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.