Our Java Application Health Check service provides an unbiased assessment of state the health of home grown and third-party java software components. We dive deeper into the architecture of the code to check whether it meets today's demands in terms of security, performance and maintainability.

Beginning the journey to embrace business solutions offered by vendors based in the Cloud as SaaS (Software as a Service) services starts with a Legacy Modernization Roadmap.  Our aim is to provide a cost-efficient carefully constructed roadmap for our clients which acts as an enabler for future SaaS integration tasks.

Usually conducted after the Java Application Health Check, the Legacy Modernization roadmap focusses on the highest priority use cases needed to extract the maximum return when pivoting towards cloud solutions.  A key aspect of the Roadmap is also providing a view on component decommissioning activities to mitigate parallel-run cost overruns.

The time-boxed Legacy Modernization Roadmap engagement outlines the key workflow integration points with "surviving" legacy systems. 

An integration blueprint is a series of concrete solution architectural artifacts which can then be used for integration development activities. 

Integration Blueprinting details the necessary alterations needed for existing APIs and defines new components and APIs where needed. We apply modern solution architecture cloud integration patterns to maximise the client's investment in the migration to Cloud-based services.

We offer our clients various engagement routes to constructing a suitable integration blueprint

• time-boxed  for a subset of mission critical use cases crucial to achieving the client's first major cloud integration milestone
• time and materials engagements for more expansive integration blueprints expressed as a series of transition architecture stages leading to our client's fully integrated target solution

Our Component and API Construction services take the Integration Blueprinting solution architecture artifacts and build concrete Java Spring Boot based applications for the client to plug into their target landscape.

We modify existing component APIs (where appropriate) and build new APIs and components as is required by the Integration Blueprint.

Our components and API deliverables are designed to be 100% compatible with the client's own CI/CD (continuous integration/continuous development) and SDLC (software development lifecycle) considerations.

Component and API engagements are time and materials based activities.