Macstab Macstab GmbH
Available for Regulated Enterprise Projects

We build systems that really perform.

Lead/Principal+ level engineers for platform, identity & performance — Kubernetes, Terraform, GitOps, Istio traffic shifting (canary/blue-green), SLO/SLA + error budgets, OAuth2/OIDC/SAML token lifecycle, observability-as-code, profiling-driven latency budgets (p99/p999). Zero-downtime patterns (stateless); near-zero / downtime-minimized migrations (stateful + DB, where feasible).

Regulated & Enterprise Experience
Reliability by design (SLO/SLA)
Zero-downtime (stateless) / near-zero (stateful+DB, where feasible)
15+
Project Experience
Tens of millions
Enterprise Scale
SLO/SLA-driven
Reliability Targets
Zero & near-zero
Rollout Patterns

Since 2009 we’ve shipped enterprise-scale production systems — including around 10M+ logins/day at peak in regulated banking, SLO/SLA-driven reliability in the high-99s (system-dependent) and zero/near-zero-downtime rollout patterns in specific projects where feasible.

Engineering Excellence

We don’t do “just code”. We design, ship, and operate systems under real constraints: regulation, auditability, performance budgets, and safe rollouts.

High-Performance Backend

Java, Kotlin, Go, Rust. Maintainable microservices, event-driven architecture, CQRS when it fits — designed for throughput, correctness, and operability.

Cloud-Native Platform

Kubernetes, Terraform, AWS/Azure/GCP. Production clusters, GitOps, Istio traffic shifting (canary/blue-green), graceful shutdown, connection draining — zero-downtime patterns for stateless; near-zero / downtime-minimized cutovers for stateful + DB (where feasible).

Identity & Security

OAuth2, OIDC, SAML. Secure auth flows, token lifecycle (rotation/revocation), session correlation, policy-driven access, Zero Trust patterns — audit-friendly by design for regulated environments.

3D & Gaming Tech

Unity, Unreal, WebGL. Real-time multiplayer backends. Physics simulations. We build immersive experiences that push hardware limits.

Performance Engineering

Profiling-first optimization: perf budgets (p99/p999), cold start/startup, memory, CPU, I/O — measured, tuned, validated under load.

Strategic Consulting

Architecture reviews, delivery playbooks, migration strategy, and technical decision-making — hands-on, production-focused, and documented.

Battle-Tested Stack

Technologies we’ve shipped and operated in production (at scale)

Java
Kotlin
Go
Rust
TypeScript
Python
Kubernetes
Docker
Terraform
AWS
Azure
GCP

Reliability & Delivery Playbook

SLO-driven engineering, progressive delivery, and operational guardrails — designed to survive production reality.

Progressive delivery (Istio)

Canary/blue-green traffic shifting, request routing, connection draining, and safe rollbacks — zero-downtime patterns for stateless services.

Stateful + DB migrations

Expand–migrate–contract, online schema changes, CDC-based cutovers, rolling upgrades, controlled failover — near-zero / downtime-minimized where feasible.

Observability guardrails

Golden signals (RED/USE), SLOs + error budgets, tracing, alert hygiene, load tests, chaos experiments — rollouts gated by metrics.

Security & compliance-by-design

OAuth2/OIDC hardening, token lifecycle, least privilege, audit trails, policy-as-code — built for regulated environments.

Real Results. Real Production.

Selected outcomes from enterprise engagements (details anonymized)

10M+
Auth events/day (peak)

In a regulated enterprise banking program: over 10 million authentication events per day at peak (e.g., year-end).

3–4×
Throughput uplift (measured)

Reduced cache round-trips and tightened the read/write path — measured higher throughput and lower latency in production-like load tests.

Audit-ready
Regulated delivery

Designed for auditability: least privilege, traceability, policy-as-code, and compliance-friendly logging/retention patterns.

Open Source · Chaos Engineering

Phase 4: Chaos Tests in CI

All articles
The Fourth Phase of Testing: Why Chaos Engineering Belongs in Your CI Pipeline
1
chaos-engineering testing ci-cd 12 min read

The Fourth Phase of Testing: Why Chaos Engineering Belongs in Your CI Pipeline

Unit tests, integration tests, container tests — and now chaos tests. We built a three-layer chaos engineering stack in C99, Java, and JUnit 5 that turns production incidents into reproducible CI gates.

Kernel-Real Fault Injection: A C99 LD_PRELOAD Chaos Library for Any Process
2
chaos-engineering c99 ldpreload 16 min read

Kernel-Real Fault Injection: A C99 LD_PRELOAD Chaos Library for Any Process

Six fault domains, zero application code changes, any ELF binary. A C99 chaos library that intercepts libc calls at the dynamic linker level — delivering kernel-real faults to Java, Go, Python, Node.js, and everything in between.

62 JDK Interception Points: In-Process Chaos Engineering with a Java Agent
3
chaos-engineering java jvm 18 min read

62 JDK Interception Points: In-Process Chaos Engineering with a Java Agent

A Java agent that instruments 62 JDK call sites using ByteBuddy. Per-test session isolation, Spring Boot 3/4 auto-wiring, and near-zero JIT overhead. Chaos engineering that runs inline in your JUnit test suite and gates the build.

From Production Incidents to JUnit 5 Annotations: A Three-Tier Chaos Testing Framework
4
chaos-engineering java junit5 20 min read

From Production Incidents to JUnit 5 Annotations: A Three-Tier Chaos Testing Framework

448 L1 syscall primitives. 92 L2 fault composites. 64 L3 production incident scenarios encoded as single annotations. A JUnit 5 extension framework that turns post-mortems into CI gates for Spring Boot, Quarkus, and Micronaut.

Ready to ship production-grade systems?

Bring your constraints. We’ll bring the architecture, delivery playbooks, and operational discipline.

Start the conversation