{"id":217,"date":"2018-04-06T18:27:41","date_gmt":"2018-04-06T17:27:41","guid":{"rendered":"http:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/?p=217"},"modified":"2018-04-09T17:30:51","modified_gmt":"2018-04-09T16:30:51","slug":"system-architecture","status":"publish","type":"post","link":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/2018\/04\/06\/system-architecture\/","title":{"rendered":"System Architecture"},"content":{"rendered":"

\"\"<\/a><\/p>\n

 <\/p>\n

The application architecture falls into the so-called \u201cThree Tier Architecture\u201d model\u00a0(click the image for zoom).\u00a0<\/i>We chose this\u00a0architectural\u00a0model in order to ensure the flexibility, security and performance of the application. The functionality is separated into three different tiers.<\/span>
\n<\/i><\/span><\/p>\n

The first is the Presentation Tier and it represents the interface (UI) of the application. The client interacts with it directly. The second segment is the Application Tier (Business Logic). It is responsible for the application functionality. The last one is the Data Tier and consists of database servers.Here the information is stored and from here it is retrieved.<\/span><\/p>\n

Presentation Tier <\/b><\/p>\n

For developing the User Interface, we will use mostly HTML, CSS, and Javascript. <\/span><\/p>\n

This tier communicates with the others by presenting the responses back to the user who made an HTTP request.It displays the information that the user is asking for, such as search results list, user profile, chat messages, etc.<\/span><\/p>\n

Because we want to offer a good user experience, the design will be colorful, yet professional and to avoid errors, we will add client-side validation for all the forms we ask users to complete.<\/span><\/p>\n

Application Tier <\/b><\/p>\n

This middle tier controls the functionality of the web application. It is focused on the server-side or backend logic.<\/span>The information displayed in the user interface (presentation tier) is received from this tier.\u00a0 It ” bridges the gap between the user interface and the underlying database, hiding technical details from the users” [1]<\/p>\n

As a technology, we chose to use node.js for the backend. It is fast, asynchronous server-side JavaScript.<\/span><\/p>\n

Data Tier <\/b><\/p>\n

“Data needed by the application logic layer are retrieved from the database, then the computation results produced by the application logic layer are stored back in the database. “[2].<\/p>\n

For the purpose of our application, we decided to use Firebase as the database. It is non-relational, schema-less,\u00a0cloud-hosted JSON database. We chose to work with it because It can synchronize data between the different clients immediately. <\/span><\/p>\n

References<\/b><\/p>\n

[1], [2]\u00a0 S.C. Chen, S. Gulati, S. Hamid, X. Huang, L. Luo, N.Morisseau-Leroy, M. D.\u00a0 Powell, C.Zhan and C. Zhang,\u00a0 “A Three-Tier System Architecture Design and Development for Hurricane Occurrence Simulation”, International Conference on Information Technology: Research and Education, 2003. Proceedings. ITRE2003, 11-13 Aug. 2003.\u00a0\u00a0<\/em><\/p>\n

Available at\u00a0 http:\/\/ieeexplore.ieee.org\/document\/1270584\u00a0(Accessed on the 09 April 2018)<\/p>\n

Author: Emanuela Colta<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

  The application architecture falls into the so-called \u201cThree Tier Architecture\u201d model\u00a0(click the image for zoom).\u00a0We chose this\u00a0architectural\u00a0model in order to ensure the flexibility, security and performance of the application. The functionality is separated into three different tiers.<\/p>\n","protected":false},"author":2964,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[23,22],"class_list":["post-217","post","type-post","status-publish","format-standard","hentry","category-tech-demo","tag-architecture","tag-design"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/posts\/217","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/users\/2964"}],"replies":[{"embeddable":true,"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/comments?post=217"}],"version-history":[{"count":16,"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/posts\/217\/revisions"}],"predecessor-version":[{"id":293,"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/posts\/217\/revisions\/293"}],"wp:attachment":[{"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/media?parent=217"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/categories?post=217"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/generic.wordpress.soton.ac.uk\/meetingofminds\/wp-json\/wp\/v2\/tags?post=217"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}