Appendix B SAmple Code • Rendering: You need to consider which type of data rendering your application requires; it is preferred to use server-side rendering frameworks because of less load time as compared with client-side rendering, and would optimize your application for web crawling. • Performance: Two-way data binding would impact the performance of the complex application, while one-way binding would not impact as much. You need to look at your requirement and the aforementioned considerations together to evaluate and decide on a framework. Integration We have chosen Apache Camel as the integration framework because it provides easy implementation of integration of a variety of different applications, which use several protocols, frameworks, and technologies. It is a lightweight mini enterprise service bus (ESB) framework that implements all enterprise integration patterns. You can use one of the following open-source frameworks to develop your integration layer: • Apache Camel • Apache ServiceMix • WSO2 ESB • Open Source Mule ESB • Open Source Talend ESB You can use open-source mini-ESB frameworks if you want to integrate two to three protocols and technologies, for example: • Reading the files • Soap to REST conversions • XML to JSON conversions • Reading or writing to data streams Otherwise you can also use commercial ESB products for large-scale integration projects. 335
![Building Digital Experience Platforms - Page 345](/cdn-cgi/image/width=600,quality=80,format=webp/https://cdn.relayto.com/images_originals/600ee85b67f67.jpeg)