MB.

E-Importer / Integrations and data synchronization

Data keeps moving. Business does not wait.

A backend system for automated export and synchronization from 1C to a web application.

E-Importere-importer.ru
Project preview: E-Importer
Company
E-Importer
Role
Fullstack Developer
Focus
Integrations and data synchronization

01 / Context

Context

Products, categories, attributes, and related records arrived from 1C and external sources in inconsistent formats. The system needed to survive network failures and unavailable sources without producing duplicates.

02 / My contribution

My contribution

  1. 01

    Built extraction, transformation, and synchronization between 1C, PostgreSQL, and the website.

  2. 02

    Developed parsers and integration services for inconsistent input formats.

  3. 03

    Implemented background jobs with retries, timeouts, and execution status tracking.

  4. 04

    Used Kafka for events and Redis for transient state and duplicate-processing protection.

  5. 05

    Added data normalization, migrations, and structured logging.

03 / Solution

Solution

The pipeline separated ingestion, validation, processing, and publishing so each stage could be retried and diagnosed independently.

Records were normalized before persistence, while job states and detailed logs exposed the exact failure point.

04 / Stack

Stack

  • Python
  • FastAPI
  • PostgreSQL
  • SQLAlchemy
  • Kafka
  • Redis
  • Docker
Next case studyGazprom ExpoDocuments under control./en/cases/gazprom-expoTelegramMessage me on TelegramA similar challenge?@hertzxqdev