Temporal gives teams one model for durable workflows, recovery, and operations instead of another collection of retry loops, outboxes, and repair jobs.
Temporal as a Common Execution Layer
Hey! 👋 I'm Dzmitry Martavoi, Co-CTO at IDT.
I architect and develop intricate distributed systems with a focus on backend development, identity & access management (IAM), and AWS Cloud infrastructure. Passionate about event-driven architectures, microservices, OAuth/OIDC, and building high-performance financial systems.
Tech Stack:
├── Languages: Go, C#/.NET, C++
├── Architecture: Microservices, Event-Driven, DDD
├── Auth/IAM: OAuth2/OIDC, Ory Kratos, Ory Hydra, AWS Cognito
├── Cloud: AWS
├── Data: Kafka, MongoDB, Couchbase, Snowflake
├── DevOps: Containers, IaC (Terraform/AWS CDK), GitHub Actions
├── APM: Grafana, Prometheus, OpenTelemetry, NewRelic
└── AI: MCP, Cursor AI, Claude Code
📄 More on the about page
💬 Reach me: Telegram |
LinkedIn |
GitHub
🎤 View my Modern C++ Presentation
Temporal gives teams one model for durable workflows, recovery, and operations instead of another collection of retry loops, outboxes, and repair jobs.
You can ship a change you could not walk through on a whiteboard. That gap has a name, and it shows up later, on a bridge, when you have to bring the context yourself.
I wanted a concrete number for whether AI tools were actually helping my work. Aggregate productivity metrics couldn't give me one. Here's the approach that finally did — and what it showed me.
How to build production-grade, fine-grained authorization in 2026 using Ory Keto — the OSS implementation of Google's Zanzibar model.
How to add OAuth2.1 authorization code + PKCE, OIDC id/access/refresh tokens, and modern security standards to an existing user base — without replacing it — using Ory Hydra.