Automated SOA Service Layer Generation for Legacy Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy computing systems are incompatible with service-oriented architecture (SOA) environments, leading to challenges in data exchange and manual, error-prone processes for creating service layers, lacking standardization, governance, and automation in service design and development.
Innovation Solution
The SOA Service Factory automates the generation of source code for SOA services by using configuration specifications, pattern templates, and DevOps pipelines to produce standardized, well-formed services that adhere to industry standards and best practices, reducing manual effort and human error.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual approach is used to develop services in service layer, then flexibility in service design is maintained, but standardization and governance control are lacking
Solution Approach 1:
The patent changes the parameter of service development from manual coding to automated code generation. Configuration specifications define service behavior parameters, and template-based generation ensures standardization while allowing flexibility through configurable parameters in the specifications.
Solution Approach 2:
The system enables self-service through automated service layer generation. The configuration specification and template engine automatically generate standardized service code without requiring manual programming, yet maintain flexibility through configurable parameters defined in the specification.
2Adaptability or versatility
If manual approach is used to develop services in service layer, then custom service design is possible, but development time and human error increase
Solution Approach 1:
Service templates and configuration specifications are prepared in advance. The template engine pre-defines service structures, interfaces, and implementations, allowing rapid generation of customized services by simply configuring parameters rather than writing code from scratch.
Solution Approach 2:
The system uses template copying to generate service code. Pre-defined service templates are copied and instantiated based on configuration specifications, enabling rapid deployment of customized services while maintaining consistency and reducing errors.
3Adaptability or versatility
If legacy systems are directly integrated with SOA environment, then system compatibility is achieved, but architectural standards are violated
Solution Approach 1:
The service layer acts as an intermediary between legacy systems and the SOA environment. It translates legacy system interfaces into standardized SOA service interfaces, ensuring both compatibility with legacy systems and compliance with SOA architectural standards.
Solution Approach 2:
The integration architecture is segmented into distinct layers: legacy system layer, service layer (with generated services), and SOA consumer layer. This segmentation allows each layer to maintain its own standards while enabling interoperability through the service layer.
4Manufacturing precision
If automated code generation is implemented, then standardization and governance are improved, but flexibility in service design may be reduced
Solution Approach 1:
The system maintains flexibility through configurable parameters in the configuration specification. While code generation is automated, users can customize service behavior by setting parameters in the configuration, allowing adaptation without manual coding.
Solution Approach 2:
The template engine provides universal service templates that can be configured for different service scenarios. A single template framework serves multiple purposes, generating various types of services while maintaining standardization, yet allowing customization through configuration parameters.
Data Source
AI summary
A system and method to automatically generate a software service to provide service layer functionalities to legacy computing systems that are inherently incompatible with a Service Oriented Architecture (SOA) consumer environment. A configuration specification defining the characteristics of the software service, including data mapping rules is received. Based on the specification, at least one pattern template for the software service is selected from a library of templates. The pattern templates provide source code patterns usable to build the software service. Source code of the software service is outputted using programming code provided in the at least one design pattern template. The outputted source code is packaged or assembled into a source code package for deployment.