Vlad

Articles

YT Cluster

link Every node accepts writes. On the Postgres you already run. Vanilla PostgreSQL plus an extension and a server process - no forked engine, no proxy in front, no managed-cloud lock-in - dbinvent.com

Released - tested and ready:

No data transfer - your database becomes a cluster node where it already sits; nothing is dumped, copied or migrated
No vendor lock - remove the extension and you are back to a single plain PostgreSQL, with your data in place
No code change - same SQL, same drivers, same extensions; a plain COMMIT is a cluster commit, with no PgBouncer and no explicit completion call
No dedicated master - nothing to promote, so nothing to fail over; a RAFT-based coordinator arbitrates and assigns workers, and never becomes the bottleneck
Writes spread across every node - transaction boundaries are derived at runtime (virtual dynamic partitioning), so disjoint writes land on different nodes
Synchronization as configuration - per-table rules decide what is redundant, what is local, and how many nodes a commit waits for: half, nodes>=N, or asynchronous
Resiliency in three layers - two-phase commit on the way in; self-healing after the fact, which re-reads, votes on and repairs a divergent copy; and a row, table or node nobody can vouch for is blocked rather than guessed
Software-defined topology (AZ, zones, tiers) - replication scope and row placement are rules, rewritten online with no redeploy or downtime
MPP analytics - Apache DataFusion planned against the declared topology, ClickHouse for columnar workloads; neither needs a copy of the data
Asking in plain language - yt_llm('...') on a local model returns PostgreSQL SQL, ClickHouse SQL or a DataFusion script, chosen by where the data lives; the model sees the catalog, never a row (how it works)
One package, not a suite - server functions (RPPD), etcd key-value, streaming and queue (etcd) and schema migration (Schema Guard) ship with the cluster

From 30 years of personal IT experience into 30 pillars of the solution - what it solves, one line each.

Measured, not asserted: 1.7x the throughput (171%) of PostgreSQL synchronous replication on a write-only load and 1.6x (162%) on an 80/20 read/write mix, at equal replication scope. Full synchronous two-phase commit across every node costs more - it is there for the tables that need it, not the default. What replication actually costs · Where Rows Live · CAP · Asking in plain language · All about YT Cluster

Schema guard

link Declarative and Imperative (Flyway inspired) DB schema management.
This Rust based opensource project is a portion of SchemaGuard complete commercial solution.

Designed for embed schema into Rust code.
Support flexible schema updates if required
Does not require history table

RPPD Rust-Python-Postgres-Discovery

Now with etcd queueing:

kdpw

link Rust-Python-Postgres-Discovery. Serverless platform for run Python code with Postgres:

Postgres extension with a trigger to notify backend service about a insert or update or delete event
Rust based opensource project with languages support (i18n)

Concurrent document modification

link When two or more users intend to modify the same JSON document in same row, they will face a delay or data corruption, but actually it’s possible to perform with a patching model.

ETCD

link Etcd server PoC for messaging queue

etcd API v3 compatible client using protobuf
Lightweight queue with order and delivery guarantee
Rust based opensource project

Decentralized Skills Exchange and Mutual Credit Network

link A search-aware framework for discovering and appreciating developers across open source, startup, and IT projects - without requiring money to change hands. Participants find each other through verified skill reputation, commit to work via signed contracts, and compensate contributions with personal credit tokens denominated in time.

Tools

Marg - MetaArgs for console rust apps

link Fewer application configuration to connection to database and store everything else in DB.

Available as cargo dependency in Rust: marg = "0.4.0"

Shims

link - Calculate sliding average Percentile and bucket size configuration support for histogram calculation.

Available as cargo dependency in Rust: shims = "0.1.0"