Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 

Repository files navigation

Petr Filippov - backend engineering and distributed systems

LinkedIn 4deus Mod GitHub followers

Distributed systems that stay correct under pressure

I am a backend engineer focused on distributed systems that move state, money, and long-running workflows safely through unreliable environments.

I design Go services from architecture to production: service boundaries, data models, consistency guarantees, asynchronous messaging, recovery workers, observability, deployment guardrails, and the operational tools needed to understand a system under pressure.

My background spans high-load products operating at up to 50k RPS, payment and settlement infrastructure, marketplace workflows, platform engineering, and backend teams built from zero. I care less about adding another service and more about making the whole system easier to reason about.

Go-first   failure-aware   architecture-to-production   operationally explicit

Engineering focus

Distributed systems Financial infrastructure Platform reliability
Consistency, idempotency, event-driven workflows, concurrency, and failure recovery Payments, payouts, settlement, reconciliation, provider integrations, and risk controls Observability, delivery automation, Kubernetes, production tooling, and guarded AI workflows

Selected work

4deus

A modular Steam Deck systems plugin spanning user interface integration, Linux input, isolated workers, guarded device recovery, localization, and deterministic release automation.

Stars Release License

A production-minded order lifecycle service demonstrating durable workflow orchestration, explicit state transitions, typed PostgreSQL persistence, API contracts, and a reproducible local environment.

A repeatable remote-debugging environment for Go applications built around Delve and Docker.

Core toolkit

Runtime and contracts

Go gRPC REST Python

State, messaging, and workflows

PostgreSQL Kafka Redis RabbitMQ Temporal

Platform and operations

Kubernetes AWS Docker OpenTelemetry Prometheus Grafana

Working principles

  • Model failure and recovery before polishing the happy path.
  • Make state transitions explicit, idempotent, and reconcilable.
  • Ship telemetry as part of system behavior, not as an afterthought.
  • Automate delivery without hiding operational risk or removing human control.
  • Keep service boundaries aligned with data ownership and team ownership.

Contact

I am always interested in difficult backend problems, open-source systems work, and conversations about architecture that survives production.

LinkedIn | 4deus Mod | 4deus Community

About

Backend engineering, distributed systems, and open-source work

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors