03 / experience

Experience in data, AI, maps, catalogues, and operational architecture

The public section contains anonymized tasks and engineering reviews: context, constraint, architecture decision, tradeoff, and outcome. Confidential client names are not published.

operating areas

Recurring problem classes in our projects

AI search, geodata, and registries need the same discipline: normalized data, clear permissions, verifiable sources, fast interfaces, and observable operations.

AI · SEARCH

Corporate knowledge and verifiable answers

Search across complex documents with cited evidence, controlled corpora, permissions, model cost, and answer quality.

corpus · search · sources · permissions

GEODATA

Maps and territorial analytics

Maps as operational tools: layers, data provenance, object search, territorial comparison, and reliable mobile use.

layers · search · geospatial analysis · mobile access

CATALOGUES

Registries and selection systems

Catalogues and registries with normalized data, deadlines, sources, filters, and controlled updates.

data model · filters · deadlines · sources

anonymized reviews

Fintech, healthtech, and commerce: three detailed scenarios

Each review records the original constraint, selected architecture, accepted tradeoffs, and operational outcome without invented testimonials or decorative metrics.

ФИНТЕХ

Financial platform: growth without downtime

How to stabilize payments, separate service responsibilities, and prepare the system for load growth.

МЕДТЕХ

Healthtech: data, access, and reliability

A review of a system where access roles, audit logs, data quality, and interface resilience are critical.

ТОРГОВЛЯ

E-commerce: catalogue, search, and performance

Catalogue, search, cache, queue, and analytics optimization for a platform with growing traffic.

engineering journal

Engineering journal on decisions and cost

The journal includes articles on AI cost, monoliths, TypeScript, RAG, Kubernetes, and PostgreSQL under load.

ИИ

How to reduce language-model costs

Routing, caching, batching, and verifiable economic impact.

API

When a monolith is better than microservices

When a monolith is cheaper, faster, and more reliable than microservices.