# Transpiler-Based Architecture Design Model for Back-End Layers in Software Development
## 4 Empirical Experiment
### Observation  
Our journey next led us to a detailed observation period characterized by both quantitative metrics and qualitative insights into the capabilities and performance of our transpiler-based architectural model, with the primary focus on the back-end. The main observation results are as follows:  
Holistic Software Realization: one of the most salient outcomes of our observational phase was the creation of complete and functional software. From its foundational layers to its user-facing components, the resulting system was not just a theoretical construct or a fragmented prototype, but a cohesive software artifact. This underscores the viability of our approach; not only can our architectural design and transpiler-based methodology be implemented in practice, it can culminate in a robust end-to-end software solution, as exemplified by our to-do-list application. The Figures 12-14 show examples of the software functionality screens. Back-end Transpilation via Haxe: Haxe demonstrated remarkable efficacy in back-end source code transpilation. The measurements highlighted variations in execution performance across the targeted back-end platforms with an impressive range of 25-60 ms per service call involving database querying, confirming its efficiency. Figure 15 presents the results of a load test of 100 requests made to the back-end targeting the method that retrieves the task list for the connected user. This was performed on a virtual machine with eight processor threads, 8 gb of RAM, and an SSD unit. The database engine was Microsoft SQL Server version 2019. Figure 12: Screenshot of the developed to-do list application (Login Screen). Figure 13: Screenshot of the developed to-do list application (Task List Screen). Efficiency of the \"Nest Implementations\": while these components acted as pivotal mediators for our back-end, they also showed compatibility with diverse infrastructural bases, such as C# (.net 4.7.2,.net core 3.1,.net core 5.0), Java (versions 8 and 11), and PHP 7. The seamless integration across these technologies testified to their robust design and flexibility. Figure 16 shows single codebase and transpiled implementations performed using different programming languages. The Task_Search method, which is used in the to-do-list application for listing and filtering the tasks that should be presented depending on the connected user, uses a single ORM implementation to help in querying the transactional database. Figure 14: Screenshot of the developed to-do list application (Task Edit Screen). Figure 15: Load test. Figure 16: Transformed code. Layered Model and Supporting Infrastructure: in addition to the sheer functionality, the efficiency of the development process was notably elevated. Although a precise numerical metric was not established, the integration of code generators allowed development efforts to be predominantly channeled into business logic and interface implementation, markedly reducing potential bottlenecks and time wastage. Figure 17 shows the physical implementation of the proposed design model, which is represented by a source code folder structure divided into layers. The equivalent component of the design model is shown on the right side. Figure 17: Design model implementation. Database Connection Objects: the readability and functionality of the objects interfacing with the database were commendable. They were easy to understand and functioned effectively. However, the insights we gathered hinted at potential areas where these could be further refined and optimized. Interactions with the Front-end: the synergy between the developed front-end (HTML, SCSS, TypeScript) and transpiled back-end was palpable. Furthermore, 100% of the initially outlined functional specification were achieved without any hitches, accentuating the robustness of the employed methodology. System Interoperability and Scalability: one of the core tenets of this research is the system's capability to function harmoniously across different back-end platforms.