JUnit Experts in Germany

Maturing their API practices on both a business and technology level. My role covers strategy, architecture, developer advocacy as well as hands-on software engineering, enabling both technical teams and business leadership to adopt and act on API-centric principles effectively. Coincidentally, we also establish GitOps, DX and platform best practices with this project.

Highlights:

• Aligning executives with the initiative by clarifying strategy, replacing misconceptions and myths with facts, clarifying the value of existing assets and enabling informed decision-making
• Formulating a way forward for API Lifecycle Management at OTTO
• Driving platform progress and fostering developer engagement by hands-on engineering work towards strategic goals

API Lifecycle Management, Team Topologies, Organizational Evolution, Regulatory, Platform Advocate, Developer Platform, Communities of Practice, Terraform, Kotlin, Kafka, Kong, WSO2, Apigee, Gravitee, Backstage, AsyncAPI, OpenAPI, API Design, AWS, React, Node.js, TypeScript, Redocly, reactive programming, CDC, Golang, Gin, GitOps, DX (developer experience), stakeholder management, roadmaps, workshops, discovery.

Built an international e-commerce platform for a multi-vendor marketplace for digital assets from scratch. Designed and operated cloud native architectures at enterprise scale.

• Designed and operated a highly scalable microservice and serverless architecture
• Built the complete cloud infrastructure with Terraform + AWS CDK in AWS
• Provisioned ECS/EKS clusters (Fargate), Application Load Balancers (reverse proxy), and Lambda functions
• Observability & tracing with CloudWatch, DataDog, Prometheus, and Grafana
• End-to-end setup with DataDog (formerly AWS CloudWatch), Prometheus, and custom Grafana dashboards
• Integration of advanced metrics (including ORM mapper) and distributed tracing with Jaeger
• Robust backup and disaster recovery strategies
• RDS Postgres backups and hourly snapshots
• Read-only, asynchronously synchronized replicas with automated master failover in emergencies
• Minute-level rollback capability through versioned Docker images on ECS and Git-based CI/CD pipelines
• Created CI/CD pipelines with GitHub Actions for automated multi-stage deployments (Dev, Testing, Prod)
• Integrated Stripe for international payment processing
• Built a marketplace payment system with multiple parties and payout routines
• Used Algolia for high-performance real-time search of digital assets on the platform
• Federation of services with GraphQL and Hasura
• Later migration to GraphQL Mesh
• Test Driven Development (TDD) - unit, integration, and E2E testing with Jest, Vitest, and Playwright
• Used Next.js / React for modern frontend applications in the nx monorepo
• Enterprise security architecture & access control
• Integration of JWT tokens with Auth0, OAuth, OIDC, IP guards, BOLA protection, and secret vaults
• Authorization concepts with RBAC, ABAC, and native Postgres Row-Level Security (RLS)
• Built internal microfrontends with Retool for fast prototyping and operational business processes

Technologies: ABAC, AWS CDK, AWS CloudWatch, AWS ECS, AWS EKS, AWS Fargate, AWS RDS, AWS S3, Algolia, Auth0, DataDog, Docker, GitHub Actions, Grafana, GraphQL, GraphQL Mesh, Hasura, JWT, Jaeger, Java, JavaScript, Jest, Kotlin, Kubernetes, Monorepo, Next.js, OIDC, Playwright, Postgres, Postgres RLS, Prometheus, RBAC, Redis, Retool, Serverless, Stripe, Terraform, TypeScript, Vitest

The Base Services of DB InfraGO form a central data hub between the company’s IT systems. Common Data Services are developed that distribute data from source systems to a variety of downstream systems (via JMS) and make them available (via REST API). The existing service landscape based on TIBCO is being migrated to DB InfraGO’s cloud-native platform.

• Architecture design and implementation for performance-optimized bulk data processing of several million datasets at specific times during the day
• Technical specification and documentation of business requirements
• Integration of various subsystems (including SAP and Salesforce) through the reimplementation of more than 40 microservices based on Spring Boot
• Migration of TIBCO Based microservices from the Enterprise Integration Platform to the Cloud Native Platform using Spring-Boot
• Establishment of a deployment pipeline using GitLab CI/CD, Artifactory, and automated deployment to a Kubernetes environment with the help of ArgoCD
• Definition and implementation of automated unit, integration, and regression tests

Team Size: 9

Technologies/Tools: Java, Spring Boot, ActiveMQ(JMS), JUnit, Tibco Business Works, Gitlab (CI/CD), Kubernetes (Amazon AWS), ArgoCD, postgreSQL, Oracle, Postman, Hoppscotch, openAPI, Sonarqube

• Fully on-premises LLM document-examination platform for a compliance-critical banking domain: agentic LangGraph pipeline with deterministic verification, every AI judgment structured and source-anchored; ~960 automated tests, zero data egress
• GPU throughput engineering (quantized serving, speculative decoding, prefix caching): 9.5x extraction speed-up, 500+ multi-document case files per day on a single A100
• AI-native EDI/EDIFACT integration platform (~116k LOC Java 25 / Spring Boot 4, 1,900+ tests): LLM-drafted partner mappings machine-verified before go-live (DFDL conformance, field-coverage checks, dry runs), ~99.5% byte match on real customer files — replacing weeks of manual mapping per partner

• Recurring problem in my own AI-assisted projects: requirements analysis, use cases, and architecture decisions can be created quickly with AI support, but remain difficult to follow and scattered across Markdown files – knowledge is lost as soon as it is no longer in the context window. arknet turns requirements engineering and architecture knowledge into structured, verifiable data instead of plain text: requirements, use cases, and architecture decisions form a consistently linked knowledge graph, traceable from requirement to architecture decision – queryable by both people and AI agents. Technically based on RDF/OWL and a custom MCP server.

• Result: Working MCP daemon, Docker image published automatically to GHCR, nine hexagonal modules, eleven ADRs (including an Open-Core licensing model). Requirements engineering and Ubiquitous Language hexagons are active. Public as a Community Edition under Apache-2.0 since 07/2026 (github.com/kogn-io/arknet), together with the Claude Code plugin and GHCR image; Open-Core model.

• Label: Java, Maven, RDF, RDF4J, OWL, SPARQL, Model Context Protocol, Spring AI, Docker, GitHub, Git, Claude Code, Obsidian, DDD, Hexagonal Architecture, ArchUnit, JUnit, AssertJ, Interface Development, Software Architecture, Continuous Integration, Knowledge Management

• Modernization of a large-scale Java enterprise application*

The project is modernizing a complex enterprise application that has grown over many years. The existing Spring-based legacy system runs on Java 8, OSGi, and Eclipse RCP and is being gradually migrated to a modern, maintainable architecture with Java 25 and Quarkus.

Marcus works on analysis, architecture, refactoring, and implementation. One focus is on untangling historically grown structures and dependencies and on building a clean, sustainable Java and Quarkus technology stack.

Tools & technologies: Java 8, Java 25, Quarkus, Hibernate ORM with Panache, EclipseLink, OSGi, Eclipse RCP, Maven, JUnit, Mockito, REST, JSON, Git, Eclipse IDE, IntelliJ IDEA Ultimate, Jira, Confluence

• Further development of the existing e-commerce platform based on SAP Commerce (Hybris) to meet the growing demands of digital commerce.
• Ensuring the scalability and performance of the backend, so the platform remained stable and efficient even under heavy user load.
• Development and integration of new OCC REST APIs and services for modular extensions and flexible adjustments, to implement new features quickly.
• Optimization of data flows and interfaces, which significantly improved platform efficiency and system performance.
• Ensuring a maintainable and scalable code base by using Clean Code principles, proven design patterns, and a future-proof architecture.
• Reduction of errors through extensive testing with JUnit, Mockito, and load tests with Gatling, supported by the introduction of automated test processes.
• Improved system performance through targeted refactoring measures and efficient database queries, especially to handle peak loads.
• Use of modern cloud and monitoring tools such as Kubernetes, Google Cloud Platform (GCP), and Grafana to ensure a stable and monitored infrastructure.
• Clear improvement in efficiency, scalability, and reliability of the platform, which now meets the demands of a dynamic and growing e-commerce market.

• Optimizing and accelera­tion of our Gitlab CI pipeline

• Conceptual work for the PoC of the Zero Trust system

• Extension of the policy-engine backend in Go

• Extension of the policy-testing mechanism in Python

• Architectural design of the PEP component of Zero Trust

• Documentation of the product

• Technologies: Zero Trust, Go, Python, Gitlab CI, Docker, JWT, Domain-Driven Design

• Building a data integration platform for high, medium, and low voltage assets for contextual analysis of time series with master data from the SCADA control system (IEC 60870 104), INIS, and SAP.
• Responsibility for the architecture and implementation of the solution, as well as sparring partner for the Product Owner.
• Use of Kotlin, Spring Boot, Maven, TimescaleDB, PostgreSQL, liquibase, Elements IoT, Docker, Kubernetes, Grafana, Python, jupyter, and various API gateways.

• Ride-sharing and bus platform, live and fully functional. Backend with Spring Boot 4.1 on Java 21, PostgreSQL with Flyway, and Testcontainers integration tests. Hosted in my own AWS account (ECS Fargate, ALB, ECR, IAM Least-Privilege) with CI/CD via GitHub Actions and OIDC federation without static credentials. Development fully AI-supported with Claude Code, including custom skills and project-specific memory. Spring Boot · Java 21 · PostgreSQL · Flyway · Docker · AWS ECS/ALB/ECR · CI/CD · GitHub Actions · Claude Code

• Client: Prime Force Group GmbH

Technologies used: Java 25, Spring Boot 4, MapStruct, JSpecify, PostgreSQL, Redis, Liquibase, REST/OpenAPI, Apache Kafka, Apache Solr, OpenID Connect via IronGate/Keycloak, SAP Customer Data Cloud, JUnit, Testcontainers, Karate, Playwright, GitLab monorepo with CI/CD, Jenkins, JFrog Artifactory, FluxCD, Docker, Kubernetes on Azure, OpenTelemetry, arc42, Jira, Confluence

The Team Management Center is the new central platform of the DFB for planning, managing, and carrying out team activities for the national teams - from squad selection and training camps to communication with players, clubs, and legal guardians. The platform is designed for multi-tenancy for the DFB and regional associations; player, club, and master data are intentionally not copied, but connected at runtime via the DFBnet APIs.

I have been involved in the project continuously since the architecture and concept phase (Sprint 0) and work in a distributed Scrum team in two-week sprints. In addition to implementation, my focus is on architecture alignment, connecting the DFBnet interfaces, as well as code reviews and test automation as quality assurance in the team.

Focus areas:

• Development and implementation of the multi-tenancy concept (tenant model for the DFB and regional associations), including data model, access layer, and Liquibase migrations.
• Design of the person service and the search concept based on Apache Solr.
• Integration of the DFBnet APIs (player, person, and club search, club data), including authentication and synchronous master data synchronization.
• Hardening the integration through resilience patterns: separate read timeouts for each search path, correction of circuit breaker counting, limiting parallel requests, and a club cache to reduce load on the external system.
• Development of self-service endpoints for players (own activities, activity details, games), including an access concept for participants, as well as person documents and file uploads.
• Standardization of API design: OpenAPI annotations, nullability model via a custom ModelConverter, JSpecify migration of the DTOs, and documented API guidelines.
• Build and maintenance of Karate-based API and integration tests, integration tests with Testcontainers, test guidelines, and bug triage from the integration and reference environments.
• Code reviews via merge requests, architecture documentation according to arc42, and architecture decisions (ADRs) in Confluence.
• Automated deployment to the integration and reference environments, analysis of login and OIDC issues in combination with IronGate.

Status: ongoing - as of 08/2026 in Sprint 17, around 940 person hours worked; testable delivery to the integration environment every two weeks.

• Training AI models, evaluating images and text UI/UX, turning the provided data into insights through OpenAI Feather as part of the machine learning workflow

Technologies: OpenAI Feather

IT consulting, analysis, architecture design, new and further development, code review, test automation, continuous integration, continuous delivery in backend and frontend areas for Automotive Project Instavalo.

Frontend:

• Implementation of UI components according to specifications, especially style guides and responsive design eith React and Typescript
• Component testing
• Code documentation
• CI/CD with Gitlab Pipeline

Backend / IoT:

• Analysis and architectural design with AWS Greengrass IoT on Edge Devices
• Setting up Microservices containers with Docker Compose on Edge device with AWS Greengrass and AWS IoT IAM, Token Exchange Service, Ansible
• CI/CD with Gitlab Pipeline, Terraform, AWS ECR
• Logging with Fluentbit Lua Language for AWS Cloudwatch
• Python Lambda for AWS Greengrass Recipe deployment on Edge Devices
• Implementation of test-driven development with JUnit, Mockito, and code Coverage
• Jacoco
• Definition of REST interfaces with OpenAPI / Swagger
• Development and enhancement of software based on Java Quarkus, Typescript NestJs NodeJs and Python
• Authentication and authorization in Aws IAM
• Development of REST and gRPC interfaces for the frontend and backend
• Implementation of Maven dependencies with DevSecOps OWASP
• Spring AI, Jetbrains AI Assistant, Junie, Github Copilot, Claude Code, Agents, Skills, Command, Hooks, Subagents

• Focus: system architecture, cloud-native platforms, microservices, API design
• Product: Pflege-Pfad is a digital matchmaking platform that connects relatives of people in need of care directly with verified care services and caregivers - without an agency and without ongoing fees.
• Business analysis & process design:
• Analysis of the German care market and identification of the key pain points of both target groups.
• Modeling of the core business processes: registration, verification, care request, application, placement, and rating.
• Definition of the business model as a freemium/premium model with optional contact unlocking.
• Creation of user stories and requirements documentation for relatives, care services, and administrators.
• Design of trust and quality assurance mechanisms with document upload, admin review process, and rating system.
• Coordination with stakeholders and validation of product decisions with potential users.
• Technical implementation:
• Design and implementation of the entire platform architecture as a solo developer.
• Design and implementation of a REST API with Spring Boot and Kotlin, including JWT-based authentication.
• Development of the frontend as a single-page application with Angular 17.
• Implementation of the AWS infrastructure with EC2, RDS PostgreSQL, S3, CloudFront, and IAM.
• Document upload with AWS S3 via presigned URLs for verification of care services.
• Email notifications via Resend API.
• AI-supported care service search via OpenAI API.
• Implementation of complete user flows such as registration, login, password reset, and placement process.
• Building an admin panel for user and care service management as well as analytics.
• CI/CD with GitHub Actions and containerized deployments with Docker.
• End-to-end tests with Playwright.

Technologies: Kotlin, Spring Boot 3, Spring Security, JWT, JPA/Hibernate, PostgreSQL, Angular 17, TypeScript, RxJS, AWS (EC2, ECS, S3, CloudFront CDN, RDS PostgreSQL, IAM), nginx, GitHub Actions, Playwright, Maven, Git, OpenAI API, Resend API, Docker, Scrum, i18n (DE/EN/TR), Kiro, feature-flag architecture.