Unified Configuration Files for Front-End and Back-End Code Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing divergence in technology stacks between front-end and back-end systems, particularly with the use of JSON and Golang, complicates the linking and synchronization of these systems, requiring recompilation and redeployment of code for modifications, making it difficult for front-ends and back-ends to implement functions simultaneously.
Innovation Solution
A data management system involving a configuration platform that generates a unified configuration file based on target environment identifiers, enabling both front-end and back-end platforms to render and generate pages and code respectively, supporting the same business environment functions without additional code development.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If front-end and back-end systems use different technology stacks (JSON and Golang), then each system can be optimized for its specific requirements, but the linkage and synchronization between systems becomes increasingly difficult
Solution Approach 1:
The patent introduces a configuration file as an intermediary that bridges the front-end and back-end systems. This configuration file serves as a common language and data exchange format between the JSON-based front-end and Golang-based back-end, enabling them to communicate and synchronize without requiring direct integration of their different technology stacks.
Solution Approach 2:
The patent segments the system into independent front-end and back-end modules that each can be developed and optimized separately using their preferred technology stacks. The configuration file acts as a boundary interface that allows these segmented systems to interact, maintaining their technical independence while achieving functional integration.
2Productivity
If modifications are made to back-end code, then the back-end functionality can be updated, but recompilation and redeployment are required which delays front-end updates
Solution Approach 1:
The patent implements preliminary action by generating the configuration file before any code changes are made. This configuration file is updated in advance to reflect the desired functionality, allowing both front-end and back-end systems to be prepared for simultaneous deployment without waiting for mutual modifications to be completed.
Solution Approach 2:
The patent uses code generation to create back-end code automatically from the configuration file, rather than requiring manual coding and recompilation for each change. This copying approach allows functional updates to be applied quickly without the time-consuming process of writing, compiling, and redeploying code for every modification.
3Adaptability or versatility
If multiple people modify code in multiple environments, then functionality can be enhanced, but coordination and synchronization become increasingly difficult
Solution Approach 1:
The patent merges the configuration management process into a single centralized location where all front-end and back-end configurations are unified. This single source of truth eliminates the need for multiple people to coordinate across different environments, as all modifications are made to one configuration file that automatically propagates to both systems.
Solution Approach 2:
The configuration file serves multiple functions simultaneously: it defines front-end page structures, specifies back-end API interfaces, and provides data mapping between the two systems. This multi-functionality eliminates the need for separate configuration files and coordination processes for each system type.
Data Source
AI summary
The present disclosure relates to a method for data management, a medium, and an electronic device. The method includes: a configuration platform obtains target configuration data configured for a target business environment corresponding to a target environment identifier, the configuration platform generates a configuration file according to the target environment identifier and the target configuration data, a front-end platform obtains the configuration file corresponding to the target environment identifier from the configuration platform, the front-end platform renders and generates a front-end page corresponding to the target business environment according to the target configuration data included in the configuration file, a back-end server obtains the configuration file corresponding to the target environment identifier from the configuration platform, and the back-end server generates back-end code corresponding to the target business environment according to the target configuration data included in the configuration file.