
Hexagonal Architecture Experts in Germany
, matched in minutes with vetted, available freelancersHire experts who design ports and adapters, isolate domain logic, and modernize Java, .NET, or Kotlin systems with Hexagonal Architecture. FRATCH matches you quickly and precisely with vetted, available freelancers for your project.
Meet FRATCH Experts in Germany, who have recently used Hexagonal Architecture
Umut A.
Last position:
Full-Stack AI Developer at DB InfraGO AG
Core developer of an internal audit platform for IS auditors. It brings together measures from the GRC tool and their audit and AI review status in one worklist, and assesses them through an AI review pipeline. FastAPI, SQLModel, PostgreSQL and React/TypeScript in a strict hexagonal architecture.
- Designed the hexagonal architecture (ports and adapters): a framework-free domain core with swappable adapters for the GRC database, RAG and LLM services, and persistence, protected by architecture tests and ADRs.
- Built the asynchronous AI review pipeline (RAG + LLM): long-running jobs on a persistent, database-backed worker, with indexing, retrieval, evaluation and aggregation stages, and LLM assessments constrained by a strict JSON schema.
- Integrated a Microsoft Fabric Lakehouse as a read-only source of truth, with transactional syncing of measures (upsert, archive, reactivate).
- Versioned report view models that trace every result to its controls, evidence chunks and sources, displayed in a printable, XSS-safe report view; frontend built with React 19, TanStack and shadcn/ui on a generated OpenAPI client.
- Type-checked and tested pipelines (mypy, ruff, pytest); kept secrets for GRC, RAG, database and LLM access out of the code.
Paul B.
Last position:
Full-Stack Developer / Software Architect at HUK Coburg
Development and further enhancement of an internal quotation system for managing and analyzing insurance policies. The focus was on consolidating existing systems, establishing modern development standards, and improving testing, security, and deployment processes. Alongside implementing new features, special attention was paid to code quality, security, and performance.
Responsibilities:
- Full-stack development of an internal quotation system based on Spring Boot and Angular
- Design and implementation of a secure Spring Security configuration, including certificate management
- Merging two bounded contexts using Domain-Driven Design (DDD)
- Introducing and integrating Testcontainers for automated integration tests
- Establishing and applying common testing methods (unit, integration, and end-to-end tests)
- Presenting and integrating Cypress as a black-box GUI testing tool
- Improving the CI/CD pipeline through automated versioning and a custom Jenkins Library
- Proof of Concept (PoC) for state management with NgRx in the frontend
- Refactoring legacy code and fixing incorrect Spring Boot configurations
- Training developers in Clean Code, best practices, and the Spring Framework
- Developing a tool to analyze test data and improve quality
- Further development of the existing Cucumber project
- Carrying out dependency updates and analyzing and maintaining the application
- Implementing telemetry and building a Dynatrace dashboard
- Improving technical documentation in line with Arc42 and introducing AsyncAPI
Technologies: Scrum, TDD, CleanCode, Spring Boot, Java, Angular, NgRx, Testcontainers, Cypress, Cucumber, Jenkins, Dynatrace, Docker, Git, Maven, Kafka, Oracle, REST, DDD, Arc42, AsyncAPI, IntelliJ, Jira, Confluence, Windows, Linux
Karthikeyan R.
Last position:
Full-Stack Developer — Own Product at Self-employed
Java 21 · Spring Boot 3 · Keycloak · PostgreSQL · Docker · Nginx · GitHub Actions · DigitalOcean · React 18 · TypeScript · Plasmo
- Architected and shipped a production-ready Job Application Tracker end-to-end: REST API with 5-stage workflow, pagination, sorting, and dynamic filtering — full ownership from design to live cloud deployment on DigitalOcean.
- Implemented production-grade identity management: OAuth 2.0 / OpenID Connect / JWT / RBAC via Keycloak, applying Hexagonal Architecture and DDD principles.
- Built automated CI/CD pipeline (GitHub Actions); containerised with Docker; Nginx reverse proxy with path-based routing and SSL termination.
- Developed a Chrome Extension (Plasmo framework, Manifest V3) that auto-fills job applications directly from LinkedIn into the tracker — demonstrates full product thinking across backend API and browser client.
Fred H.
Last position:
Software Architect and Developer at Personal project
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
Ibrahim H.
Last position:
Senior Full Stack / AI Engineer at Punktum Digital GmbH
- Context: Healthcare and laboratory teams required faster document analysis, treatment-planning support, and reliable AI workflows for MR/VR-assisted operations.
- Contribution: Built the AI healthcare platform, model/agent workflows, VR-glasses deployment platform, REST APIs, Next.js/React interfaces, and CI/CD pipelines.
- Impact: Delivered a production-ready AI product foundation that improved clinical document review, supported laboratory automation, and made VR fleet deployment manageable across environments.
Tech: TypeScript, Next.js, Node.js, React, Java, Spring Boot, Python, PyTorch, TensorFlow, Docker, PostgreSQL, OpenAPI, GitLab, GitHub Actions.
Armin J.
Last position:
Managing Director/Partner at Disolpa GmbH
Mark P.
Last position:
Full-Stack Software Developer, Product Data Import at Otto (GmbH & Co KG)
- Manage and operate the product data import services for the Otto merchant
- Enhance and maintain the backend systems
- Optimize and maintain AWS infrastructure
- Build a new product data import API
- Design and plan stories and features
- Conduct code reviews to ensure code quality and best practices
- Analyze and fix bugs
- Technologies: Java, Spring Boot, Kafka, AWS, Fargate, Terraform, MongoDB, Mongo Atlas, OpenAPI, GitHub, GitHub Actions, GitHub Copilot, Akhq, Debezium, JUnit, Test Containers, Hexagonal Architecture
Marcus B.
Last position:
Java and Quarkus Expert at Large German energy service provider
- 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
Robert H.
Last position:
Technical Lead – Java Backend & AI-Augmented Delivery at Conrad Electronic
Delivering two large, complex strategic initiatives in parallel with an 8-person team – OCFA (platform migration and consolidation of the cart-checkout backend) and Conrad PRO (a new paid loyalty/membership programme) – with agentic AI development as the team's standard way of working rather than an experiment on the side. Set technical direction, engineering standards and quality gates across both, hands-on in the codebase throughout.
Agentic development as the delivery model:
Introduced LLM-based development (Claude Code, Gemini) as the core team workflow and built the agent tooling behind it – custom Claude Code skills encoding the team's coding standards so generated code arrives conformant, multi-agent sub-agents for code review and legacy-parity checking, and a scheduled diff-monitoring loop watching the legacy system for changes. CI build time dropped by ~36%, and the team sustained roughly two production changes per day: 38 parity and feature tickets closed via 39 reviewed and merged MRs in a representative four-week window.
Quality ownership over AI output:
Every agent-generated change passed the same gates as any other – automated tests, parity validation and SonarQube – with human review before merge. Speed came from the agents; accountability for what shipped stayed with the team.
Java backend & legacy-parity migration:
Java 25 and Spring Boot 4 with Spring Modulith, structured around hexagonal architecture and DDD. Defined the shadow-testing strategy for legacy-parity correctness – reverse-engineering undocumented legacy contracts and validating against real production traffic – through to shadow-parity readiness for the first live country cut-over (Netherlands).
Enterprise integration:
Integrated downstream systems (SAP, payment, pricing/offer, shop-config) via contract-first OpenAPI and outbound adapters, using Kafka and Pub/Sub for asynchronous messaging.
Stack: Java 25, Spring Boot 4, Spring Modulith, Hexagonal Architecture / DDD, Contract-First OpenAPI, Kafka, GCP Pub/Sub, SAP integration, PostgreSQL, GitLab CI/CD, SonarQube, Claude Code, Gemini
Olaf N.
Last position:
Frontend Engineer at Danaher/Hach Lange GmbH
- Developed a SolidJS frontend UI for a spectrometric water analysis system on an ARM-based embedded Linux platform
- Prototyped UI in TypeScript React/Nx with LitElements and MQTT integration
- Built production UI using SolidJS, SUID, i18next, Ajv, MQTT.js, C3.js
- Refined requirements with UX team and water analysis system engineers
- Defined and documented system architecture, MQTT message formats, frontend architecture, and development setup
- Set up frontend system from scratch, implemented domain-oriented type system, UI components, and application state
- Managed MQTT pub/sub services and schema-based message validation in frontend
- Coached two junior frontend developers
- Worked in an agile remote team using JIRA, Git, and Bitbucket
Muthukumar K.
Last position:
Senior Java Backend Developer at Upwork
- Developed Java 21 / Spring Boot 3.2 microservices with REST and GraphQL APIs for GDPR-compliant consent workflows using Hexagonal Architecture
- Enhanced Backend-for-Frontend (BFF) performance using AI-assisted tools for code refactoring and optimization
- Built event-driven workflows with Kafka, RabbitMQ, AWS SQS, and integrated Salesforce Marketing Cloud for real-time consent tracking
- Implemented OAuth2 and Keycloak security, automated CI/CD with Jenkins, GitHub Actions, and Gradle, and deployed containerized services on Docker and Kubernetes with AWS and Azure
- Executed unit, integration, and contract testing with JUnit 5, TestNG, Mockito, and TestContainers; monitored performance via Grafana, Kibana, and AWS CloudWatch
- Developed microservices for digital identity verification and e-signature management with Hexagonal Architecture
- Integrated Keycloak 24.x with OAuth2.1 and OpenID Connect for SSO and RBAC, ensuring EU eIDAS compliance
- Designed API-first microservices with OpenAPI 3.1, Swagger, and GraphQL for improved interoperability
- Automated CI/CD pipelines with Jenkins, GitHub Actions, and Gradle; deployed containerized services on AWS EKS and Azure; monitored with Grafana, Kibana, CloudWatch, and TestContainers
Alexandr E.
Last position:
Software/Solution Architect at Robert Bosch GmbH
- Designed and implemented scalable software and system architectures, improving cross-domain collaboration and reducing time-to-market for “EV Charging” domain
- Aligned with stakeholders and defined architectural guidelines, ensuring consistency and high-quality solutions across teams
- Established arc42 as the standard for architecture documentation, improving transparency and maintainability of complex systems
Tejasvi Y.
Last position:
Backend Engineer at N26
- Developed and maintained Kotlin-based microservices with Kafka event streaming, applying Hexagonal Architecture and Domain-Driven Design in production environments.
- Contributed to the Bring-Your-Salary feature, enabling seamless onboarding of new salary accounts and improving customer experience.
- Built and integrated services for the FPAD VOP platform, supporting secure and scalable partner integrations.
- Investigated and resolved production incidents through root cause analysis (RCA), implementing fixes that improved service stability and reliability.
Michael W.
Last position:
TUI AG / Robinson
- Development of an Internet Booking Engine IBE (Saber and Juniper) and other microservices
- Backend development with PHP and Symfony, endpoint and interface implementation
- Unit and integration testing
Osman T.
Last position:
Senior Architect, DevOps Engineer at genPsoft GmbH
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
Discover over 15,000 top freelancers
Statistics of experts using Hexagonal Architecture
Aggregated from the professional profiles of matched freelancers.
Experience
18 years

Position duration
1.4 years

Positions per freelancer
15

Top business areas
Information Technology, Product Development, Quality Assurance

Top industries
Information Technology, Banking and Finance, Automotive

Certification focus areas
Information Technology, Product Development, Project Management
Bachelor's degree or higher
95%
Master's degree or higher
60%
Doctorate
10%

Certifications per freelancer
2

Most common languages
English, German, Spanish

Speak two or more languages
97%
Based on our profile pool as of 18 Nov 2026.
Daily rate distribution
The chart shows how the daily rates of experts in this technology in Germany are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows the share of experts charging within that range.
Average rates of experts in Germany using Hexagonal Architecture
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 18 Nov 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
Hexagonal Architecture experts industry focus
See which industries our matched freelancers work in most often — every figure is calculated live from the freelancers on FRATCH.
- Information Technology (100%)
- Banking and Finance (69%)
- Automotive (59%)
- Insurance (41%)
- Transportation (41%)
- Manufacturing (41%)
- Government and Administration (38%)
- Retail (38%)
Please note that freelancers can work across multiple industries, so percentages overlap.
About the technology
What Hexagonal Architecture is
Hexagonal Architecture organizes software around its business logic rather than its databases, user interfaces, or external services. Also called Ports and Adapters, it places the application core at the center and connects outside systems through clear interfaces. This separation makes dependencies point inward and keeps domain rules easier to test and change.
What it builds
The approach suits business-critical applications that must evolve without constant rewrites. It is common in customer platforms, payment services, order processing, logistics systems, and internal tools built with Java, Kotlin, .NET, or similar ecosystems.
- Domain-driven application cores
- REST and messaging integrations
- Services prepared for cloud deployment
- Legacy systems split into replaceable components
Ports, adapters and tooling
A port defines what the application needs or exposes; an adapter connects that contract to a technology such as PostgreSQL, Kafka, REST, GraphQL, or a user interface. Strong implementations use dependency injection, automated tests, contract tests, and modular build tools. Spring Boot, .NET, Maven, Gradle, Docker, and Kubernetes often appear around the architecture, but none defines it alone.
When companies need expertise
Freelance expertise helps when a system has business rules scattered across controllers, persistence code, and integrations. It is also valuable during a migration from a monolith, a platform split, or a redesign where delivery must continue while boundaries are introduced.
- Map existing dependencies and business capabilities
- Define application, driving, and driven ports
- Replace tightly coupled infrastructure adapters
- Establish testing and migration steps
What strong professionals deliver
Experienced specialists distinguish meaningful domain boundaries from layers created only for appearance. They document decisions, keep interfaces focused, and select adapters that fit operational needs. Their deliverables may include a target architecture, dependency map, reference modules, migration plan, test strategy, and review guidance for the internal team.
Collaboration in Germany
Companies in Germany use this approach across industrial operations, finance, healthcare, retail, and software products where reliability and long-term maintainability matter. Remote collaboration works well for architecture reviews, repository changes, and documentation; on-site workshops can help when domain discovery involves several business teams. Clear technical English is common, while German may matter for stakeholder workshops and regulated environments.
Frequently asked questions
Questions about Hexagonal Architecture? Start with the answers below.
Hexagonal Architecture is used to keep business rules independent from databases, interfaces, messaging systems, and other external tools. It supports applications that need frequent change, strong automated testing, and replaceable integrations.
Hexagonal Architecture and Clean Architecture both protect the application core from infrastructure concerns. Onion Architecture expresses a similar dependency direction through concentric layers, while Ports and Adapters emphasizes the contracts and connection points around the core. The practical result depends more on boundary quality than on the label.
A strong Hexagonal Architecture specialist usually understands domain-driven design, dependency inversion, API design, event-driven integration, and automated testing. Experience with Java, Kotlin, .NET, Spring Boot, messaging, containers, and cloud operations can be useful when those technologies surround the application core.
The right level depends on the scope. A focused adapter or module may need a specialist who can apply the pattern within an existing codebase, while a full migration requires someone comfortable with domain discovery, legacy constraints, technical decision-making, and incremental delivery.
Yes. Hexagonal Architecture can be introduced gradually by identifying a business capability, extracting its use cases, defining ports, and moving infrastructure behind adapters. This avoids requiring a complete rewrite and lets the team validate each boundary as the system evolves.
Remote work is practical for repository analysis, architecture sessions, implementation, and code reviews. Hexagonal Architecture projects may still benefit from on-site workshops when specialists must map complex business processes with German-speaking stakeholders or coordinate across several departments.
Ask for examples of boundaries they introduced, trade-offs they documented, and migration steps they delivered. A capable Hexagonal Architecture professional explains why a port exists, keeps the domain free from infrastructure details, and shows how tests verify the intended dependency direction.
No. Ports and Adapters provides a useful structure, but excessive abstraction can slow delivery and make simple systems harder to understand. Quality comes from purposeful boundaries, clear domain language, suitable adapters, and architecture that matches the system’s actual change needs.
The average hourly rate of freelancers in Germany who have used Hexagonal Architecture in their recent projects is 96 €, which corresponds to a daily rate of about 766 € based on an 8-hour working day.
Of the freelancers in Germany who have used Hexagonal Architecture in their recent projects, 95% hold at least a Bachelor's degree, 60% hold at least a Master's degree, and 10% hold a doctorate.
On average, freelancers in Germany who have used Hexagonal Architecture in their recent projects have 18 years of professional experience, with a single engagement typically lasting around 1.4 years.
The most common languages among freelancers in Germany who have used Hexagonal Architecture in their recent projects are English (100%), German (97%), and Spanish (10%).
The most common industries among freelancers in Germany who have used Hexagonal Architecture in their recent projects are Information Technology (100%), Banking and Finance (69%), and Automotive (59%).
The most common business areas among freelancers in Germany who have used Hexagonal Architecture in their recent projects are Information Technology (100%), Product Development (100%), and Quality Assurance (69%).
Main locations of FRATCH Experts, who have recently used Hexagonal Architecture
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Berlin