Gateway Consumption Framework for Enterprise Application Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing software applications that interface with a back-end system is challenging for developers unfamiliar with the back-end system, leading to a steep learning curve, increased costs, and potential errors due to the need to understand the schema and business logic.
Innovation Solution
A gateway consumption framework that provides user interface templates and business logic definition parameters, allowing developers to create applications through a user interface while protecting the back-end system, using a framework with layers for user interface logic, business logic, data definitions, and data instances, and utilizing OData for data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If developers directly interface with the back-end system, then they can access data and functions, but they need steep learning curves and deep knowledge of schema and business logic
Solution Approach 1:
The patent introduces a front-end adapter layer that serves as an intermediary between the developer's application and the back-end system. This adapter handles complex back-end interactions, schema mappings, and business logic translations, allowing developers to work with simplified interfaces while the adapter manages the complexity of interfacing with the back-end system.
Solution Approach 2:
The patent segments the system into distinct layers: a simplified front-end interface layer for developers and a complex back-end system layer. The front-end adapter acts as a boundary that separates these layers, allowing each to be developed and maintained independently while reducing the learning curve for developers working at the front-end layer.
2Productivity
If developers unfamiliar with the back-end system create applications, then development costs increase and errors increase, but using familiar developers reduces these risks
Solution Approach 1:
The front-end adapter serves as a protective intermediary that enforces proper interaction patterns with the back-end system. It validates inputs, handles errors systematically, and ensures that applications regardless of developer expertise follow correct protocols, thereby maintaining reliability while enabling faster development by less experienced developers.
Solution Approach 2:
The patent implements error handling and validation mechanisms in advance within the front-end adapter. By preparing error templates, validation rules, and fallback procedures beforehand, the system cushions against potential errors that might occur during application development, reducing the error rate even when developers are unfamiliar with the back-end system.
3Adaptability or versatility
If developers directly access the back-end system, then they can implement custom logic, but they may accidentally harm the back-end system
Solution Approach 1:
The front-end adapter acts as a protective barrier that filters and validates all interactions between applications and the back-end system. It implements security checks, authorization validations, and transaction management that prevent harmful operations while still allowing legitimate custom logic to be executed, thus protecting the back-end system from accidental harm.
Solution Approach 2:
The patent implements preventive measures in the front-end adapter that counteract potential harmful actions before they reach the back-end system. This includes input validation, SQL injection prevention, authentication checks, and transaction rollback mechanisms that neutralize potential threats while preserving legitimate application functionality.
Data Source
AI summary
According to some embodiments, a method and apparatus are provided to display to a developer, a list of business application user interface templates. A selected user interface template from the displayed list of business application user interface templates is received. Business logic definition parameters are also received. Based on the selected user interface template and the received business logic definition parameters, potential services available to be consumed by a business application from a suite of enterprise applications is determined and an indication of the list of potential services to the developer device is transmitted.