LOGIC TELECOM
Tech worldAugust 12, 20262 min read

SIBUR moves part of its data platform to Arenadata Hyperwave and Streaming

SIBUR moved part of its enterprise data platform to Arenadata Hyperwave and Streaming: over 100 systems, about 50,000 messages per second and more than 150 queues.

Industrial data streams converge on a resilient storage core
Contents

On 11 August 2026, Arenadata reported that SIBUR had moved part of its corporate data platform from a foreign vendor’s system to Arenadata Hyperwave and Arenadata Streaming. The scope stores data and exchanges it among internal systems.

Confirmed scale

The official announcement says the platform handles data from more than 100 information systems. Arenadata Streaming carries about 50,000 messages per second across over 150 queues, while the busiest queues reach 2,500 messages per second.

Listed use cases include process-control and IIoT data, equipment diagnostics, research, video monitoring, mobile inspections, data quality and environmental reporting. A SIBUR representative also states that production-process messages are delivered with delays of up to 30 seconds.

Throughput is not the whole reliability model

An average message rate does not describe a streaming platform’s operating envelope. A migration should also test:

  • P95/P99 delay and oldest-record age;
  • recovery after a consumer stops;
  • ordering and duplicate handling;
  • offset recovery and queue state;
  • topic permissions and administrative audit;
  • schema evolution and reader compatibility;
  • rollback for each migrated stream.

Transport SLOs should be separated from business freshness. A record may enter a queue quickly yet wait in transformation, quality control or downstream loading.

Migrate in waves

Move groups of streams with common owners and requirements rather than the whole platform at once. For each wave, record source and target schemas, control totals, allowed variance, parallel-run duration and the condition for disabling the old path.

Critical streams can be read from both environments temporarily and compared outside the business process. Dual writing without explicit event keys and reconciliation can itself produce duplicates.

Remaining limitations

The vendor announcement includes customer figures but does not disclose project duration, cost, the exact share migrated or independent load tests. The stated rates cannot be generalised without message size, partitioning, replication and consumer-workload data.

See enterprise integration architecture and infrastructure observability for the surrounding practices.

Source: Arenadata’s official announcement dated 11 August 2026.

Primary source: Arenadata: SIBUR data-platform migration

InfrastructureIntegrationsArchitectureResilience

Read also