Senior Solutions Architect — Application Modernisation

We are modernising a portfolio of legacy line-of-business applications — spanning Oracle APEX / PL/SQL and mainframe workloads — into cloud-native Java / Spring Boot services with an Angular front end, running on AWS EKS. Mainframe migration and decommissioning is one of our major local IT initiatives. This is primarily an analysis, discovery and planning role spanning both the APEX and mainframe estates. The architect leads assessment, owns the target architecture, migration patterns, decommissioning plan, sequencing and risk picture, and partners with mainframe SMEs for deep COBOL-level analysis. Hands-on architecture and design governance are part of the job, but day-to-day build leadership is not the main focus - candidates looking for a pure delivery-lead role are unlikely to be a fit. We are building AI tooling and internal accelerators to speed up legacy code comprehension, translation and parity testing, and you'll have access to mainframe SMEs for deep COBOL-level analysis. We want someone who treats those as force multipliers - and who has ideas about how to make them better. Assessment & discovery (primary focus) Lead discovery of the legacy portfolio: inventory applications, map data and integrations, and document the business logic - much of it undocumented - embedded in the source systems. Reverse-engineer Oracle APEX applications (pages, processes, computations, validations, shared components and server-side PL/SQL) to recover the true behaviour of the system, not just the database schema. Analyse mainframe workloads in the same way - COBOL / PL-I programs, JCL batch flows, VSAM data and CICS transactions - working with mainframe SMEs to recover business rules and data lineage from code where documentation is thin. Assess each workload for complexity, coupling, data sensitivity and migration risk, and classify it against the right strategy: retire, rehost, replatform, or refactor / re-architect. Produce the assessment artefacts the programme runs on: application inventory, dependency and data-flow maps, integration catalogue, and effort / complexity estimates. Use AWS Schema Conversion Tool (SCT) and Database Migration Service (DMS) to assess Oracle → PostgreSQL schema and PL/SQL conversion effort and surface conversion blockers early. Target architecture & migration strategy Define the end-to-end target architecture for migrating workloads to Java / Spring Boot microservices with an Angular front end, deployed to AWS EKS. Design scalable, resilient, secure cloud-native architectures following the AWS Well-Architected Framework; select appropriate services (Aurora PostgreSQL, EKS, API Gateway, SQS / SNS, EventBridge, Lambda, S3). Develop reusable migration patterns, reference architectures and blueprints - including the strangler-fig pattern for incremental cutover - so approaches are consistent across streams. Define the data and logic migration approach: schema conversion, relocation of PL/SQL business logic into services, and re-platforming of batch jobs. Sequence the migration into waves with explicit dependencies, producing a phased roadmap that keeps the business running throughout cutover. Mainframe migration & decommissioning Choose the right per-workload strategy across the mainframe estate - rehost / replatform / refactor / retire - balancing risk, cost and the decommissioning timeline.

… lees de volledige omschrijving bij ZZP-Opdrachten.nl.