DESIGNING SCALABLE SYSTEMS
Michał Makowski
Platform Engineer | Distributed Systems | AI Integration
I design scalable cloud platforms, enabling reliable event-driven systems and AI-powered workflows for production-grade, high-throughput environments.
- • Designed event-driven AI processing architecture for asynchronous workloads improving scalability and resilience (Azure Service Bus, background workers)
- • Built multi-service cloud platform for production-grade, scalable systems with reliable deployment and maintainability (.NET 9, Clean Architecture, CI/CD, Bicep)
- • Implemented real-time LLM-based evaluation pipelines for automated data processing and system feedback
Archora Platform
Archora
Strategic control center for architecture evolution
Archora is the core platform for CTOs and architects to design, govern, and evolve distributed systems. It connects architecture maps, dependency flow, API contract control, and risk visibility in one operating model.
- Archora Core — Acts as the architectural source of truth for domains, service boundaries, ownership, and dependency topology.
- Archora Intelligence — Transforms architecture telemetry into actionable insights, exposing hotspots, coupling trends, and structural drift risks.
- Archora Governance — Enforces architecture guardrails, decision policies, and review workflows to keep system evolution aligned with platform strategy.
- Archora Flow — Coordinates cross-domain architecture change flow, ensuring dependencies and sequencing are explicit before implementation starts.
- Archora Risk — Quantifies architectural risk exposure, prioritizes remediation, and links risk posture directly to delivery planning.
- Archora Contracts — Governs API and integration contracts, detects breaking deltas early, and drives contract-safe change propagation.
- Archora Maps — Maintains a live architecture map of services, relationships, and ownership context to support system-wide impact analysis.
- Archora Tasks — Closes the architecture-to-delivery gap by generating implementation tickets from architecture analysis, enforcing contract/dependency-driven changes, and operationalizing architecture decisions in delivery backlogs.
Profile
Platform-first engineering
I design and own resilient cloud systems with clear architectural boundaries, reliable operations, and measurable impact.
I operate at the intersection of platform engineering and product delivery, designing systems that remain stable under real production load.
I take end-to-end ownership — from architecture and infrastructure to implementation and rollout — ensuring technical decisions directly impact reliability, performance, and delivery speed.
- Design systems around asynchronous, queue-driven processing to improve scalability and fault isolation
- Apply reliability patterns (retries, idempotency, observability) as first-class design concerns
- Own systems end-to-end, ensuring they operate effectively in production, not just in development
Reliability-first
Systems are designed to operate under real-world conditions, with explicit handling of failure, observability, and long-term operational stability.
Event-driven thinking
I design systems around asynchronous, event-driven architectures and decoupled components to improve scalability, fault isolation, and system resilience.
End-to-end ownership
From architecture to deployment and production support, I ensure systems are designed, delivered, and operated effectively in real-world environments.
Platform enablement
I build platforms and tooling that enable teams to deliver faster, reduce operational friction, and scale systems consistently across the organization.