# Transpiler-Based Architecture Design Model for Back-End Layers in Software Development
## 3 Transpiler-Based Design Model for Back-End Layers
### Detailed Design
#### 3.4.4 Automated Process  
In Figure 6, it is possible to see the elements of the automated process proposed for each of the operationalization and instrumentation stages of the architecture approach.  
This is designed as a plug-in utility that is executed immediately after the transpiler completes the code translation process. The objective is to prepare the transpiled source code to adapt it to the execution models and compile it in order to make it ready for deployment. This processing is necessary because the source code produced by the transpiler is not directly usable as a standard back-end service, and requires the following three steps:  
* Preparation Process Starting from the raw transpiled source code, this process executes cleanup processes, splits the code into separate components, generates source code for native service frameworks, prepares for configuration file support, and handles special source code cases and other requirements specific to each supported target programming language. The detailed process is explained in Figure 7. The implementer should consider all post-transpilation processing required to obtain the final code. This code is then automatically compiled by calling the native compilers of each technology to obtain the final artifacts usable on the target platform with all its deployment elements.  
Figure 6: Automated process diagram.  
* Nest Implementation Placement The transpiled source code, having passed the preparation process and runtime artifacts, must be placed inside a generic solution that has specific elements of the target technology and supported architecture design. This generic solution is prepared to receive the transpiled code, and is characterized by being compatible with development kit libraries. Finally, the code is automatically moved to the development application server, allowing the developer to begin the testing stage. These native solutions are called \"Nest Implementations\"; the greater the number of these solutions that exist in the framework, the greater the diversity of ways to generate native artifacts starting from the same business logic. After this stage, the back-end layer is ready for deployment and execution. The final product consists of native artifacts compiled from different programming languages and prepared for different execution technologies.
* Back-End Proxies Although the back-end layer of the application was already built in the previous step and is operational, and although the development of the front-end layer is not the main focus of this proposal, it is nonetheless necessary to generate the source code of the service consumption layer. This allows for a reduction in the front-end developer programming time. During this process, business logic objects corresponding to data transport and business logic invocation methods that are exposed should be automatically generated. In addition, this process must incorporate a base library that encapsulates the call methods and support components. A proxy layer must be generated for each supported front-end technology. The generated back-end proxies are considered the \"Client Side Library\".