DevOps & automation
I turn manual build, deployment and infrastructure tasks into repeatable workflows with explicit checks, permissions and recovery steps.
Independent engineer · Munich, Germany
I connect business applications, messaging systems and data flows so that teams can change their systems without losing control of the interfaces between them.
Discuss your requirementsA legacy interface, manual data transfer or undocumented dependency can block a new application or migration. The first task is to make the existing contracts, failure paths and ownership visible before changing them.
For a replacement interface, agree the message or API contract, map the existing data, test normal and failed deliveries, and define reconciliation before moving traffic. A cutover and rollback plan belongs to the same delivery scope.
Middleware products, versions, network access and third-party responsibilities are agreed before implementation. Product licensing, vendor support and uninterrupted migration are not implied by a consulting engagement.
Review my published projects and technical expertise to assess the fit for your systems. The project descriptions show the actual work; technology selection and availability are confirmed for your engagement.
Published engineering projects · Technical expertise · Professional background
An incremental approach can preserve existing systems while replacing selected interfaces. Its suitability depends on the contracts, dependencies and ability to test and roll back each change.
Describe the source and target systems, data flow, middleware versions, current failures and access restrictions. Start with a summary; confidential data and credentials are not needed in the contact form.
Share the systems involved, the problem to solve, the expected delivery window and your access or security constraints. A short initial summary is enough to assess the next step.
Discuss a project