# Transpiler-Based Architecture Design Model for Back-End Layers in Software Development
## 5 Discussion
### About the Related Articles  
A comparative analysis was conducted on multiple articles related to the proposed research with the objective of examining how the proposed design model aligns with or differs from the existing literature in the field of software development. We performed this analysis to enhance the applicability and potential impact of the proposed approach and to identify potential areas for further research and development. * SequalsK--A Bidirectional Swift-Kotlin-Transpiler [51] This scientific article addresses the challenges of developing apps separately for iOS and Android platforms and the pros and cons of using cross-platform development frameworks. The authors suggest a native development approach that takes advantage of the similarities between the Swift and Kotlin programming languages. They propose bidirectional transpiling of the model part of an app, which enables developers to work on a shared model using their preferred language. The proposed SequalsK transpiler supports the critical constructs of both languages and produces correct syntax and semantics. Through a case study, this article shows that the model part of a board game app can be transpiled in both directions without limitations, with little manual effort required to derive an Android version from a Swift version. The proposed approach is different from using transpilers for back-end development in that it focuses on the model part of the app and enables joint development by iOS and Android experts. This approach does not focus on the back-end. * FLY: A Domain-Specific Language for Scientific Computing on FaaS [52] The authors of this article explored the use of Function-as-a-Service (FaaS) in cloud computing for the development and execution of large-scale scientific computing applications, proposing a domain-specific language named \"FLY\" for designing, deploying, and executing such applications using the FaaS service model on different cloud infrastructures. This paper presents the design and language definition of FLY on various computing back-ends, and introduces the first FLY source-to-source compiler available on GitHub that supports SMP and AWS back-ends. The FLY language and FaaS service model offer an opportunity for easy development and execution of large-scale scientific applications with fine-grained application decomposition and efficient scheduling on cloud provider infrastructure. The use of FLY is different from a software architecture design that uses transpilers to develop back-end layers, as FLY employs FaaS and a specialized language designed specifically for scientific computing applications. * OP2: An Active Library Framework for Solving Unstructured Mesh-Based Applications on Multi-Core and Many-Core Architectures [53] This article discusses the OP2 library, a framework that allows developers to transform unstructured mesh-based applications into parallel implementations for execution on different hardware platforms. This paper presents the design and features of OP2, including its recent extension to the distributed memory clusters of GPUs, and highlights the main design challenges for parallelizing unstructured mesh-based applications on heterogeneous platforms. The authors used a CFD application written using the OP2 framework for benchmarking and performance analysis on various platforms, demonstrating that OP2 can achieve near-optimal performance without the intervention of domain-application programmers. It should be noted that OP2 is distinct from a software architecture design that uses transpilers for back-end development, which focuses on facilitating the development of back-end layers using transpilers and language interoperability for shared codebase development, whereas OP2 provides source-to-source translation and compilation framework for execution on different hardware platforms and is specifically designed for unstructured mesh-based applications.