WebSocket Service for 1C-Bitrix and Bitrix24

In our practice, a typical Bitrix e-commerce site updates cart stock with a 2-5 second delay. The customer adds an item, but the system hasn't recalculated availability yet. An hour later, an email arrives: 'item out of stock'. WebSocket solves this by maintaining a persistent connection and delivering data instantly. Push notifications for e-commerce — one of the key scenarios we implement. WebSocket is a standard for bidirectional communication (Wikipedia). We offer choosing the right architecture: Centrifugo, Ratchet, or Node.js. Let's break down what and when to choose, and how to integrate without headaches.

The problem with polling

Instead of the browser asking every N seconds "any new data?", WebSocket keeps a single persistent connection. With 1000 simultaneous users and a 5-second interval, polling creates 200 requests per second — most empty. WebSocket sends data only when it appears, reducing server load by 10-15 times and saving up to 40% of server resources (estimated $500/month savings on typical cloud hosting). Long polling is a compromise but scales worse and consumes more memory. In practice, WebSocket handles up to 10,000 simultaneous connections on a single server without performance loss, with response times under 50ms.

Choosing a WebSocket server for Bitrix

The stack choice determines development speed and maintenance cost. Below is a comparison of three approaches without marketing promises.

Technology comparison

Centrifugo is suitable for a quick start: a ready server with channel authorization, message history, and scaling. You get a production-ready solution in a couple of days, but less flexibility — you need to adapt to its API. Ratchet, on the other hand, gives full control: you write connection logic in PHP, integrate directly with Bitrix. The downside — you'll need to implement authorization and error handling manually. Node.js + Socket.io is for high-load projects with thousands of connections. It's a separate stack, integration via Redis pub/sub, but performance is 2-3 times higher compared to Ratchet.

For a typical e-commerce store with 200 orders per day, Centrifugo is enough. If you need a complex chat with history and moderation — choose Node.js. With a limited budget and full customization — Ratchet. Experience shows that the right choice reduces total cost of ownership by 40%.

Architecture with Centrifugo

Centrifugo is a separate service, Bitrix interacts with it via HTTP API:

Browser ←→ WebSocket ←→ Centrifugo ←→ Redis
                                         ↑
                               Bitrix publishes events

When an event occurs in Bitrix (new order, status change) — PHP code publishes to a Centrifugo channel:

$centrifugo = new CentrifugoClient('http://centrifugo:8000', $apiKey);
$centrifugo->publish('orders:' . $managerId, [
    'event' => 'new_order',
    'order_id' => $orderId,
    'customer' => $customerName,
    'amount' => $amount,
]);

The browser, subscribed to the channel orders:{managerId}, instantly receives the event. Channel authorization via JWT — Centrifugo checks permissions through a Bitrix endpoint.

Architecture with Ratchet

For tighter integration — a custom WebSocket server on Ratchet. Run as a daemon:

php /local/cli/websocket_server.php

// websocket_server.php
use Ratchet\Server\IoServer;
use Ratchet\Http\HttpServer;
use Ratchet\WebSocket\WsServer;

$server = IoServer::factory(
    new HttpServer(
        new WsServer(
            new BitrixWebSocketHandler()
        )
    ),
    8080
);
$server->run();

BitrixWebSocketHandler implements \Ratchet\MessageComponentInterface:

• onOpen — new connection, authorization
• onMessage — message from client
• onClose — close
• onError — error

Connection storage: SplObjectStorage with mapping user_id → connection. Communication with Bitrix via Redis pub/sub — Bitrix publishes, Ratchet reads and distributes.

How to integrate WebSocket with Bitrix?

Integration consists of several steps. Let's use Centrifugo as an example — the most common choice.

1. Install and configure Centrifugo. Run a Docker container, specify API key and JWT secret.
2. Set up authorization. Create an endpoint in Bitrix that returns a JWT token for the current user. Centrifugo checks the token on each connection.
3. Publish events. In Bitrix event handlers (e.g., OnOrderAdd), call the Centrifugo HTTP API to publish to the appropriate channel.
4. Frontend client. Connect via WebSocket, pass the token, subscribe to channels, and handle messages.
5. Deploy with Supervisor and Nginx. Ensure auto-restart and proxying.

Frontend: connecting to WebSocket

const ws = new WebSocket('wss://example.com:8080');

ws.onopen = () => {
    ws.send(JSON.stringify({ type: 'auth', token: userJwt }));
};

ws.onmessage = (event) => {
    const data = JSON.parse(event.data);
    if (data.event === 'new_order') {
        showNotification(`New order #${data.order_id} for ${data.amount} ₽`);
    }
};

ws.onclose = () => {
    setTimeout(() => connectWebSocket(), 3000);
};

Auto-reconnect with exponential backoff is mandatory. Mobile networks are unstable.

What is included in the work

• Scenario analysis and technology selection
• WebSocket server setup (Centrifugo/Ratchet/Node.js)
• Integration with Bitrix via Redis pub/sub
• Frontend client development (JS, authorization, reconnection)
• Deployment with Supervisor and Nginx
• Connection metrics monitoring
• Architecture and support documentation
• Deliverables: detailed architectural documentation, server access credentials, a 2-hour training session for your team, and 1 month of post-launch support

Development stages

When is WebSocket justified?

WebSocket is justified where a delay of a few seconds is critical for UX. For notifications that can be shown upon the next page transition — it's overkill. We will assess your project for free — just contact us.

To speed up the choice: if you have up to 1000 simultaneous connections and typical scenarios (notifications, cart updates) — choose Centrifugo. If you need a custom protocol or integration with PHP logic — Ratchet. For large-scale chats and collaborations — Node.js. Get a consultation from our engineer — we'll help design the architecture.

With over 5 years of experience and certified Bitrix developers, we guarantee 99.9% uptime for your WebSocket service.

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.