畢業(yè)設(shè)計(jì)外文資料翻譯-對(duì)PHP的MVC框架演變的實(shí)證研究

1、畢業(yè)設(shè)計(jì)外文資料翻譯學(xué) 院： 專業(yè)班級(jí)： 學(xué)生姓名： 學(xué) 號(hào)： 指導(dǎo)教師： 外文出處： Advanced Computer and Communication Engineering Technology 附 件：1.外文資料翻譯譯文； 2.外文原文 指導(dǎo)教師評(píng)語(yǔ)：該英文資料選擇合理，與畢業(yè)設(shè)計(jì)論文相關(guān)度較高。專業(yè)術(shù)語(yǔ)、詞匯翻譯的準(zhǔn)確度較高，體現(xiàn)了較強(qiáng)的專業(yè)英語(yǔ)應(yīng)用水平。翻譯工作認(rèn)真細(xì)致，嚴(yán)格按照規(guī)定，翻譯材料基本能與原文能保持一致，能正確表達(dá)出原文意思，細(xì)節(jié)處理得當(dāng)，保持準(zhǔn)確。翻譯字、詞數(shù)滿足要求。翻譯材料語(yǔ)句較通順，符合中文的表達(dá)習(xí)慣。翻譯工作能夠嚴(yán)格按照規(guī)定，達(dá)到考核、提高學(xué)生英語(yǔ)應(yīng)用水

2、平的目的，圓滿完成要求。簽名： 年 月 日1外文資料翻譯譯文對(duì)PHP的MVC框架演變的實(shí)證研究摘要：網(wǎng)絡(luò)技術(shù)的貿(mào)易，社會(huì)和教育的重要性已經(jīng)極大的提高在網(wǎng)絡(luò)編程腳本方面的研究。關(guān)于編寫(xiě)PHP解碼的幾個(gè)方法，例如：面向?qū)ο蟪叹幊蹋ê?jiǎn)稱：OOP），PHP編碼程序和模型視圖控制器（簡(jiǎn)稱：MVC）模式已經(jīng)被提出。模型視圖控制器（簡(jiǎn)稱：MVC），發(fā)展PHP應(yīng)用最重要的方法之一，有許多變形，例如：Laravel, Symfony, CodeIgniter, CakePHP等等。然而，在變形之中對(duì)于MVC框架最好的選擇與程序設(shè)計(jì)者和項(xiàng)目經(jīng)理密切相關(guān)，特別是當(dāng)解決重大應(yīng)用問(wèn)題時(shí)。因此，需要性能評(píng)價(jià)準(zhǔn)則。這篇文章

3、討論MVC，基于最著名的PHP框架，評(píng)估它們的性能，并且發(fā)現(xiàn)Laravel執(zhí)行其他MVC框架。因此，Laravel被提出是在未來(lái)網(wǎng)絡(luò)技術(shù)最適用于PHP框架的技術(shù)。簡(jiǎn)介基于應(yīng)用的網(wǎng)絡(luò)，互聯(lián)網(wǎng)的迅速發(fā)展顯示著對(duì)解碼方法的可信度，可測(cè)量性，安全性以及可維護(hù)性的更高的需求。PHP，是一個(gè)使得動(dòng)態(tài)互動(dòng)網(wǎng)絡(luò)發(fā)展的編譯程序，例如：使用簡(jiǎn)便的編譯快捷，跨平臺(tái)，開(kāi)放資源，靈活性和所需的最小安裝程序。這變成最重要的網(wǎng)絡(luò)發(fā)展語(yǔ)言之一，因此，PHP是網(wǎng)絡(luò)世界中最有力的程序設(shè)計(jì)語(yǔ)言。幾個(gè)發(fā)展者選擇有效地利用基于PHP的應(yīng)用，將所有的問(wèn)題，例如：數(shù)據(jù)存取，業(yè)務(wù)邏輯以及數(shù)據(jù)顯示層都揉合在一起。這樣相應(yīng)的創(chuàng)造了發(fā)展問(wèn)題，特別

4、是對(duì)于大的工程項(xiàng)目。為了解決這些問(wèn)題，MVC設(shè)計(jì)模式帶來(lái)了最有效的方式，從對(duì)方根據(jù)每層活動(dòng)層獨(dú)立編碼。MVC設(shè)計(jì)模式被證實(shí)是發(fā)展應(yīng)用程序，例如：CakePHP, CodeIgniter, Laravel, Symfony的最有效方法。MVC最主要的方式是分離應(yīng)用到各個(gè)層面，這樣可以獨(dú)立運(yùn)行，并且產(chǎn)生同樣的效果。使用MVC模式的優(yōu)勢(shì)：標(biāo)準(zhǔn)性，連續(xù)性和可預(yù)測(cè)性；軟件組件或者結(jié)構(gòu)構(gòu)建以便于發(fā)展者可分享和重新使用解碼；一個(gè)模型和體系結(jié)構(gòu)可允許整個(gè)系統(tǒng)如何工作的簡(jiǎn)單可視化；可在文庫(kù)，教室里的重新使用和徹底檢測(cè)的解碼作用；結(jié)構(gòu)良好的解碼可適用于體系結(jié)構(gòu)模式；安全性，互用性和可維持性；盡管基于框架結(jié)構(gòu)的MV

5、C(CakePHP, Laravel, CodeIgniter)有許多優(yōu)點(diǎn)，但是，對(duì)于最好的PHP框架的選擇仍是一個(gè)憂慮。這是因?yàn)樗械目蚣懿粫?huì)覆蓋網(wǎng)絡(luò)應(yīng)用的所有層面。這個(gè)學(xué)習(xí)研究評(píng)估最著名的PHP框架是基于MVC設(shè)計(jì)模型，并且它的執(zhí)行以及為未來(lái)網(wǎng)絡(luò)發(fā)展提出最有效的PHP,MVC框架。材料和方法模型視圖控制器（簡(jiǎn)稱：MVC）的操作方法是分離或者拆分不同部分的解碼變成不同的層次，例如：視圖，數(shù)據(jù)存取，控制使用者需求以及提出對(duì)相關(guān)層面的要求。 MVC模式的稱謂對(duì)三個(gè)核心部分的總結(jié)：模型，視圖，控制器。一個(gè)完整的，正確的MVC模式的視覺(jué)表現(xiàn)類似于下面的圖形。模型模型這個(gè)稱謂得名于使用在整體設(shè)計(jì)時(shí)數(shù)據(jù)

6、的長(zhǎng)期儲(chǔ)存。它必須允許數(shù)據(jù)被查看，被收集和被編寫(xiě)的權(quán)利，并且它在整體模式中充當(dāng)著視圖部分和控制器部分的橋梁作用。模型最重要的一個(gè)部分在于它是技術(shù)上的文盲因?yàn)檫@樣，模型在當(dāng)它被傳送給視圖或者是控制器的時(shí)候，它對(duì)于數(shù)據(jù)發(fā)生了什么是沒(méi)有聯(lián)系或者是了解的。它從不命令或從其他部分尋找回復(fù)，它最主要的目的是處理數(shù)據(jù)而使之能長(zhǎng)期儲(chǔ)存，以及準(zhǔn)備數(shù)據(jù)能被傳送到另外的部分。模型不能被簡(jiǎn)單的認(rèn)定為數(shù)據(jù)處理基礎(chǔ)工具，或者是看成處理數(shù)據(jù)的另一個(gè)系統(tǒng)的入口。模型是數(shù)據(jù)自身的一個(gè)看管者，不問(wèn)任何問(wèn)題，只接受所有要使用到它的需求。常常在MVC系統(tǒng)里這種最復(fù)雜的部分，模型部分也是整個(gè)系統(tǒng)的頂峰，如果沒(méi)有它，在控制器與視圖之間也

7、不會(huì)有任何聯(lián)系。視圖視圖是一個(gè)數(shù)據(jù)的功能區(qū)，它是模型層數(shù)據(jù)的輸出展示。傳統(tǒng)意義上，為了發(fā)展而在網(wǎng)絡(luò)應(yīng)用中使用MVC。視圖是系統(tǒng)的一個(gè)組成部分，在其中產(chǎn)生并顯示出了HTML。視圖也引發(fā)了使用者們的反響，他們?cè)诳刂破髦谢?dòng)交流。這個(gè)最基礎(chǔ)的例子是由視圖產(chǎn)生的按鈕，可以讓使用者在控制器中單擊并觸發(fā)一個(gè)行動(dòng)。關(guān)于視圖的錯(cuò)誤認(rèn)識(shí)這里列舉出幾個(gè)關(guān)于視圖部分的錯(cuò)誤認(rèn)識(shí)，尤其是被網(wǎng)絡(luò)發(fā)展者應(yīng)用在MVC模式中去構(gòu)建他們的應(yīng)用。比如，許多人誤認(rèn)為視圖與模型之間沒(méi)有任何的聯(lián)系，以及所有由視圖所顯示的數(shù)據(jù)都是傳送給控制器。事實(shí)上，這種言論與MVC模式背后的理論是完全相悖的。Fabio Cevascos的文章，Cake

8、PHP框架：你的第一錯(cuò)誤印象證實(shí)了在CakePHP框架中這種存在疑惑性的方式。為了正確應(yīng)用MVC結(jié)構(gòu)，在視圖與模型之間必須不存在任何的相互影響：所有的操作規(guī)則都由控制器制定。進(jìn)一步來(lái)說(shuō)，把對(duì)于視圖的表述看成是一個(gè)模版文件是不準(zhǔn)確的。視圖確實(shí)不僅僅是一個(gè)模版，MVC框架的現(xiàn)代啟發(fā)已經(jīng)幾乎退化成一種觀念，沒(méi)有人真正的關(guān)心一個(gè)框架是否能真正的堅(jiān)持正確的MVC模式。對(duì)于提及視圖部分從沒(méi)有由控制器而被迫傳輸數(shù)據(jù)也是很重要的。如果在視圖與控制器之間不存在模型，那么這兩者是沒(méi)有直接的聯(lián)系的。控制器三個(gè)組成部分中的第三個(gè)部分是控制器。它的工作是處理使用者所傳送的數(shù)據(jù)，以及相應(yīng)地更新模型?？刂破骺梢员豢偨Y(jié)成是一

9、個(gè)信息收集員，然后它將信息傳送給模型儲(chǔ)存，并且不包含任何操作規(guī)則，不同于收集使用者的輸入信息?？刂破饕矁H被連接在一個(gè)獨(dú)立的視圖和模型上，使之只有一個(gè)數(shù)據(jù)傳送系統(tǒng)，并且在數(shù)據(jù)交換的每一個(gè)點(diǎn)都有確定的程序。當(dāng)使用者首先與視圖進(jìn)行交流時(shí)，控制器就會(huì)被授予任務(wù)去執(zhí)行，并且每一個(gè)控制器都能起到觸發(fā)器的作用，在使用者與視圖交流時(shí)而被設(shè)置。發(fā)展者所犯的最普遍的錯(cuò)誤是，把控制器誤認(rèn)為是一個(gè)入口，并且最終指定視圖應(yīng)該做履行的作用和責(zé)任。另外，有一個(gè)普遍錯(cuò)誤是去指定控制器的作用是大量處理信息，傳送和處理從模型到視圖的數(shù)據(jù)。盡管如此，MVC模式關(guān)系應(yīng)該在模型與視圖之間被維持。CodeIgniterCodeIgnit

10、er是一個(gè)開(kāi)放型資源高速發(fā)展的網(wǎng)絡(luò)應(yīng)用框架，為的是與PHP一同構(gòu)建動(dòng)態(tài)網(wǎng)絡(luò)。它的目標(biāo)是能夠比Scratch編寫(xiě)的解碼更加快速的發(fā)展專題項(xiàng)目。通過(guò)為普遍所需的任務(wù)提供大量的文庫(kù)和簡(jiǎn)單的界面以及邏輯結(jié)構(gòu)去進(jìn)入這些文庫(kù)。CodeIgniter第一個(gè)公共的版本在2006年，2月28日被發(fā)布。最新的穩(wěn)定版本2.1.4在2013年7月8日被發(fā)布。CodeIgniter大致是被基于通俗化的模型視圖控制器發(fā)展模式。然而發(fā)展CodeIgniter視圖與控制器是一個(gè)必要的組成部分，模型是可以選擇的。當(dāng)與其他PHP框架相比，CodeIgniter的速度是引人注目的。CakePHPCakePHP是一個(gè)開(kāi)放型資源網(wǎng)絡(luò)應(yīng)

11、用框架。它接受模型視圖控制器（簡(jiǎn)稱：MVC）方式以及被編程進(jìn)PHP。CakePHP使用最著名的微軟工程概念和微軟設(shè)計(jì)模式。SymfonySymfony是MVC應(yīng)用程序的一個(gè)PHP網(wǎng)絡(luò)應(yīng)用框架。Symfony是一個(gè)免費(fèi)的微軟程序，并且在MIT協(xié)議下被發(fā)布。The 在2005年10月18日被運(yùn)行。LaravelLaravel是一個(gè)PHP免費(fèi)開(kāi)放資源網(wǎng)絡(luò)應(yīng)用結(jié)構(gòu)，這個(gè)設(shè)計(jì)是為了MVC網(wǎng)絡(luò)應(yīng)用的發(fā)展。Laravel是在MIT協(xié)議下被發(fā)布。Benchmarking為了評(píng)估所涉及到的四個(gè)PHP框架（CodeIgniter(簡(jiǎn)稱：CI), Symfony, CakePHP 和Laravel）的運(yùn)行。實(shí)施Be

12、nchmarking的最有效方法是通過(guò)制定幾個(gè)準(zhǔn)則，例如：每秒所需，平均系統(tǒng)負(fù)荷，使用內(nèi)存和每個(gè)MVC所需的大量文件。為了評(píng)估這四個(gè)框架，網(wǎng)絡(luò)設(shè)計(jì)包含hello word在APACHE中被執(zhí)行，這是每個(gè)評(píng)估準(zhǔn)則下的結(jié)果。每秒所需（Request per Second） 這種Benchmarking是基于APACHE。數(shù)字圖40.2展示了在四個(gè)MVC（CodeIgniter(簡(jiǎn)稱：CI), Symfony, CakePHP 和Laravel）中的不同運(yùn)行?？梢钥吹降氖?，在所需人數(shù)上，Laravel比其他的幾個(gè)MVC的數(shù)量要多。相比于其他幾個(gè)，它可以每秒處理3000個(gè)需求。在這種情況下，因此，更大

13、的輸出暗示著更好的結(jié)果，以及暗示著最好的執(zhí)行效果。平均系統(tǒng)負(fù)荷（System Average Load）平均系統(tǒng)負(fù)荷是與時(shí)間有關(guān)的測(cè)量方式，那就是，在一分鐘內(nèi)當(dāng)Apache Benchmark完成后，在這種情況下，最小是最好的。數(shù)字圖40.3展示了一分鐘內(nèi)四個(gè)MVC在系統(tǒng)負(fù)荷方面的比較。在這個(gè)圖表內(nèi)，Laravel用了最少的時(shí)間?；谄骄鶗r(shí)間，最少的平均時(shí)間能夠更好的運(yùn)行MVC應(yīng)用。結(jié)論一個(gè)圍繞PHP框架，以MVC模式為主的實(shí)驗(yàn)性研究在本論文中被評(píng)估。這些結(jié)果從評(píng)估四個(gè)框架（CodeIgniter(簡(jiǎn)稱：CI), Symfony, CakePHP 和Laravel）中得出，并且在每個(gè)框架中使用

14、了每秒所需，平均系統(tǒng)負(fù)荷，內(nèi)存使用，大量所需文件和可以利用的設(shè)備。它顯示出Laravel優(yōu)于其他的MVC框架。相比于，其他的像CakePHP平均每秒只能讀取750個(gè)需要，而Laravel可以平均每秒讀取高達(dá)3000個(gè)所需。這個(gè)結(jié)果的得出，來(lái)自于其他所有的決定性因素，例如：儲(chǔ)存，大量的文件，反應(yīng)時(shí)間等等，暗示著Laravel有著網(wǎng)絡(luò)應(yīng)用發(fā)展的巨大靈活性。對(duì)于編程人員來(lái)說(shuō)，它擁有更多的設(shè)備。在不同的準(zhǔn)則（如：開(kāi)放資源，靈活性）下，它對(duì)于所有的網(wǎng)絡(luò)編程人員來(lái)說(shuō)都是易于獲得的。它提供簡(jiǎn)單的程序遷移，豐富的文庫(kù)，模版系統(tǒng)，有說(shuō)服力的ORM源代碼以及廣范圍的聯(lián)合支持，這些可以幫助順利地發(fā)展應(yīng)用。Larav

15、el所有的準(zhǔn)則和設(shè)備都證明，基于網(wǎng)絡(luò)應(yīng)用而有效地發(fā)展下一代PHP，Laravel將是所有選擇之中的最佳選擇。2.外文原文An Empirical Study of the Evolution of PHP MVC FrameworkRashidahF.Olanrewaju, ThouhedulIslamandN.AliAbstract Commercial, social and educational importance of web technology has tremendously increased research activities in web programming/s

16、cripting. Several methods for writing PHP codes such as Object Oriented Programming (OOP), Procedural PHP coding and Model View Controller (MVC) pattern have been proposed. Model View Controller (MVC) which is one of the most powerful method for developing PHP application has many variant such Larav

17、el, Symfony, CodeIgniter, CakePHP etc. However, selection of best MVC framework among the variants is of concern to the programmers as well as project managers, espe- cially when managing big applications. Hence, performance evaluation criterions are required. This paper discusses the MVC based most

18、 famous PHP frameworks, evaluate their performance and it was found that Laravel outperforms other MVC framework, hence Laravel is proposed as the most suitable PHP framework for future web technology.40.1 IntroductionThe rapid development of internet for web based application indicates a higher dem

19、and of reliability, scalability, security and maintainability of coding methodology. PHP, a scripting tool for web that enable dynamic interactive web development such intuitive, compiled fast, cross platform, open source, exibility as well as required minimal setup 1. This became one of the importa

20、nt web development language thus, PHP is one of the most powerful programming language in the web world. Several developers choose to deploy application based on PHP putting all the issues such as data access, business logic, and data representation layer together2.This in turn create development pr

21、oblems especiallyfor big projects. To solve this problem, MVC design pattern brings an effective ways to separate code in layers from each other based on each layer activities.MVC design pattern is aproven effective way to develop application such as CakePHP, CodeIgniter, Laravel, Symfony. The main

22、methods of MVC to spilt an application into separate layer that can work separately and produce same result. The advantage of using MVC patternare: Standard, consistency and predictability Software components or building-blocks so that developers can share and reuse code3 A model or standard archite

23、cture that allows easy visualization of how the entire system works4 Reusable and thoroughly tested code in the libraries, classes and functions. Well-structured code using architectural pattern6. Security, interoperability and Maintenance.Although MVC based framework (CakePHP, Laravel, CodeIgniter)

24、 has number of advantages 7, however, selecting of best PHP framework is still a concern. This is because all of the framework does not cover all aspect of web applications. This study evaluate most famous PHP frameworks based on MVC design model and it performance as well as proposed the best efcie

25、nt PHPMVC framework for future web development.40.2 Materials and MethodsThe operation of Model View Controller (MVC) method is to spilt or separate the different parts of code into layers such as view, data access, controlling users requests and forward request to relevant layers 8. The MVC pattern

26、s title is a collation of three core parts: Model, View, and Controller. A visual representation of a complete and correct MVC pattern looks like the following in Fig. .1 ModelThe Model is the name given to the permanent storage of the data used in the overall design. It must allow access for the da

27、ta to be viewed, or collected and written to, and is the bridge between the View component and the Controller component in the overall pattern 9. One important aspect of the Model is that its technically blindby this, the model has no connection or knowledge of what happens to the data when it is pa

28、ssed to the View or Controller components 10. It neither calls nor seeks a response from the other parts of the component; its main purpose is to process data into its permanent storage, seek and prepare data to be passed along to the other parts. The Model cannot simply be assumed as a database too

29、lkit only, or a gateway to another system which handles the data process 11. The Model represents a gatekeeper to the data itself, asking no questions but accept all requests which comes its way. Often this most complex part of the MVC system, the Model component is also the pinnacle of the whole sy

30、stem since without it there will be no connection between the Controller and the View.40.2.2 ViewThe View is a module where data, requested from the Model is viewed and its nal output is determined. Traditionally in web application use MVC for development, the View is the part of the system where th

31、e HTML is generated and displayed. The View also ignites reactions from the user, who then goes on to interact with the Controller. The basic example of this is a button generated by the View, which a user clicks and triggers an action in the Controller. Misconceptions About ViewThere are some misco

32、nceptions held about View components, particularly by web developers using the MVC pattern to build their application. For example, many mistaken the View as having no connection whatsoever to the Model and that all of the data displayed by the View is passed from the Controller. In reality, this ow

33、 disregards the theory behind the MVC pattern completely. Fabio Cevascos article, The CakePHP Framework: Your First Bite 1 demonstrates this confused approach to MVC in the CakePHP framework. In order to correctly apply the MVC architecture, there must be no interaction between models and views: all

34、 the logic is handled by controllers 13. Further- more, the description of Views as a template le is inaccurate. The View is really much more than just a template, the modern MVC inspired frameworks have bastardised the view almost to the point that no one really cares whether or not a framework act

35、ually adheres to the correct MVC pattern or not. Its also important to mention that the View part is never given data by the Controller. There is no direct relationship between the View and the Controller without the Model in between them.40.2.3 ControllerThe third component of the triad is the Cont

36、roller. Its job is to handle data the user submits as well as update the Model accordingly. The Controller can be summed up as a collector of information, which then passes it on to the Model to be organized for storage, and does not contain any logic other than collecting user input 9. The Controll

37、er is also only connected to a single View and to a single Model, making it a one way data ow system, with handshakes and signoffs at each point of data exchange. Controller is only given tasks to perform when the user interacts with the View rst, and that each Controller function is a trigger, set

38、off by the users interaction with the View 14. The most common mistake made by developers is confusing the Controller as a gateway, and ultimately assigning it functions and responsibilities that the View should do (this is normally a result of the same developer confusing the View component as a te

39、mplate).Additionally, its a common mistake to assign the Controller functions that gives it the sole responsibility of crunching, passing, and processing data from the Model to the View. Nonetheless, the MVC pattern relationship should be kept between the Model and the View.40.3.1 CodeIgniterCodeIgn

40、iter is an open source rapid development web application framework, for use in building dynamic websites with PHP. Its goal is to enable to develop projects much faster than writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and l

41、ogical structure to access these libraries. The rst public version of CodeIgniter was released on February 28, 2006, and the latest stable version 2.1.4 was released July 8, 2013 15. CodeIgniter is loosely based on the popular Model-View-Controller develop- ment pattern. While view and controller cl

42、asses are a necessary part of develop- ment under CodeIgniter, models are optional. CodeIgniter is most often noted for its speed when compared to other PHP frameworks.40.3.2 CakePHPCakePHP is an open source web application framework. It follows the Model- View-Controller (MVC) approach and is writt

43、en in PHP, modeled after the con- cepts of Ruby on Rails, and distributed under the MIT License 16. CakePHP uses well-known software engineering concepts and software design patterns, as Convention over conguration, Model-View-Controller, Active Record, Association Data Mapping, and Front Controller

44、.40.3.3 SymfonySymfony is a PHP web application framework for MVC applications. Symfony is free software and released under the MIT license. The website was launched on October 18, 200 LaravelLaravel is a free, open source PHP web application framework, designed for the development of MVC web applic

45、ations. Laravel is released under the MIT license, with its source code hosted on GitHub. The key design points of Laravel are: Bundles provide Laravel with a modular packaging system, and numerous bundled features are already available for easy addition to applications. Eloquent ORM is an advanced

46、PHP implementation of the active record pat- tern, providing internal methods for enforcing constraints to the relationships between database objects 18. Application logic is part of developed applications, either by using controllers, or as part of route declarations. Syntax used for denitions is s

47、imilar to the one used by Sinatra framework. Reverse routing denes a relationship between links and routes, making it possible for later changes to routes to be automatically propagated into relevant links. When links are created by using names of existing routes, appropriate URIs are automatically

48、created by Laravel 19. Restful controllers provide an optional way for separating the logic behind serving HTTP GET and POST requests. Class auto loading provides automated loading of PHP classes, without the need for manual maintenance of inclusion paths. On-demand loading prevents loading of unnec

49、essary components; loaded are only those components which are actually used 20. View composers are logical code units that can be executed when a view is loaded. Migrations provide a version control system for database schemas, making it possible to associate changes in the applications code base an

50、d required changes in the database layout, easing deployment and updating of applications 21. Unit testing plays an important role in Laravel, which itself has a large number of tests for detecting and preventing regressions. Unit tests can be run through the artisan command-line utility 22. Automat

51、ic pagination simplies the task of implementing pagination, replacing the usual manual implementation approaches with automated methods inte- grated into Laravel 23.40.4 BenchmarkingTo evaluate the performance of four mentioned PHP frameworks; CodeIgniter (CI), Symfony, CakePHP and Laravel. The best

52、 way to do the benchmarking is by applying several criteria such as request per second, system load average,memory usage, number of function calls and number of les required on each of the MVC. To evaluate these four frameworks, web design which contains hello word was carried out on apache (ab c 20

53、0 n 50,000), below are results of each evaluation criteria.40.4.1 Request per SecondThis benchmarking is based on apache (ab c 200 n 50,000). Figure 40.2 shows the performance comparison among four MVC: CI, CakePHP symphony and Laravel. It can be seen that Laravel outperforms other MVC in terms of request person. It was able to handle 3,000 request per second compare to others. In this case, bigger output indicates perfect result hence, it denotes bes