Please use this identifier to cite or link to this item:
http://ir.juit.ac.in:8080/jspui/jspui/handle/123456789/10245
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Chaturvedi, Saksham | - |
dc.contributor.author | Sidhu, Jagpreet Singh [Guided by] | - |
dc.date.accessioned | 2023-10-07T10:40:29Z | - |
dc.date.available | 2023-10-07T10:40:29Z | - |
dc.date.issued | 2023 | - |
dc.identifier.uri | http://ir.juit.ac.in:8080/jspui/jspui/handle/123456789/10245 | - |
dc.description | Enrollment No. 191220 | en_US |
dc.description.abstract | The three layers are handler, service and datastore which are all independent of each other. The handler layer receives the request body and then parses anything that is required from that request. It then calls the service layer where all the logic of the program is defined, ensures that the response is the required format and writes it to the response writer. This layer further communicates with the datastore layer. It takes whatever it needs from the handler layer and then calls the datastore layer. The datastore layer is where all the data is stored. It can be any data storage. The use case layer is the only layer that communicates with the datastore. That is how we test each layer independently making sure that no layer affects the other. | en_US |
dc.language.iso | en_US | en_US |
dc.publisher | Jaypee University of Information Technology, Solan, H.P. | en_US |
dc.subject | Web Application | en_US |
dc.subject | Three layered architecture | en_US |
dc.title | Web Application in Go using Three Layered Architecture | en_US |
dc.type | Project Report | en_US |
Appears in Collections: | B.Tech. Project Reports |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
Web Application in Go using Three Layered Architecture by Saksham Chaturvedi.pdf | 2.31 MB | Adobe PDF | View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.