About Me
Hi, I'm Yuri
I'm Senior Software Engineer with 17+ years building end‑to‑end products: backend services in Node.js / TypeScript and user interfaces in React / Next.js. Based in Riga. I design service boundaries, data flows, deployment pipelines—and the frontend hooks that make them useful.
Recent work includes EV charging platform integrations (OCPI / Hubject OICP) and refactoring legacy code paths for maintainability. Core interests: microservices vs modular monolith trade‑offs, API design (REST / GraphQL), performance profiling (hot paths, I/O, allocations), observability, and reliable delivery (CI/CD, rollout safety, runtime ergonomics).
Full‑Stack & Platform Highlights
- Designed Node.js (Express / NestJS) APIs (REST & GraphQL) consumed by React/Next.js clients
- Built modular CMS + personalization platform (microservices + microfrontends)
- Implemented microfrontend composition and shared UI contracts
- Containerized & deployed workloads (AWS ECR/ECS, App Runner, CloudFront, Terraform)
- Improved runtime visibility (structured logs, tracing, metrics) reducing MTTR
- Optimized latency & throughput (caching layers, connection reuse, query/index tuning)
- Hardened CI/CD (parallel test tiers, rollout safety, automated quality gates)
- Mentored engineers across backend, frontend & mobile; drove architectural reviews
- Refactored legacy modules to clearer ownership & test boundaries
- Improved local environment setup with Docker to reduce onboarding time
Core Stack
Backend / Services
Node.js, TypeScript, Express, NestJS, Strapi, Laravel, REST, GraphQL, Microservices
Data & Storage
PostgreSQL, MySQL, Cassandra, MongoDB, Redis (cache), File/Object storage
Platform & Ops
Docker, Kubernetes, AWS, GCP, Terraform, CI/CD (GitHub Actions, CircleCI), pm2, Observability
Frontend
React, Next.js, Vue.js, React Native
Books which I would recommend
A few titles that shaped how I think about code, architecture, and professional discipline:
- Clean Code – Naming, small functions, readability over cleverness.
- The Clean Coder – Professional conduct, discipline, saying no when needed.
- Clean Architecture – Separation of concerns, dependency direction, testable core.
- Clean Agile – Principles and values over rigid ceremony; iterative discipline.
(All by Robert C. Martin)
Guiding Principles
- Evolve architecture; avoid premature abstraction
- Instrument early: logs, traces, metrics guide decisions
- Readable over clever
- Small, reversible steps reduce risk
- Healthy teams build healthy systems
Get in Touch
Feel free to reach out if you'd like to discuss anything related to software development, have questions about my posts, or just want to connect.