Please use this identifier to cite or link to this item: http://ir.juit.ac.in:8080/jspui/jspui/handle/123456789/10251
Full metadata record
DC FieldValueLanguage
dc.contributor.authorBharota, Rishabh-
dc.contributor.authorHooda, Diksha [Guided by]-
dc.date.accessioned2023-10-07T10:53:52Z-
dc.date.available2023-10-07T10:53:52Z-
dc.date.issued2023-
dc.identifier.urihttp://ir.juit.ac.in:8080/jspui/jspui/handle/123456789/10251-
dc.descriptionEnrollment No. 191237en_US
dc.description.abstractA web application may be made rather easily, but testing, structuring, cleaning, and maintaining the code is a barrier. To address this, we use the Go language and adhere to the Three Layered Architecture. The three layers—handler, service, and datastore—are separate from one another. After receiving the request body, the handler layer parses it for any necessary information. The response is then written to the response writer after the service layer, where the program's entire logic is defined, has been called. Additionally, this layer converses with the datastore layer. It invokes the datastore layer after taking what it requires from the handler layer. All of the data is kept in the datastore layer. Any data storage device can be used. The only layer that interacts with the datastore is the use case layer. This is how we test each layer separately to make sure they don't affect one another.en_US
dc.language.isoen_USen_US
dc.publisherJaypee University of Information Technology, Solan, H.P.en_US
dc.subjectZopstoreen_US
dc.subjectThree layered architectureen_US
dc.subjectWeb Appen_US
dc.subjectDockerizeen_US
dc.titleZopstore Web App Built using Three Layered Architectureen_US
dc.typeProject Reporten_US
Appears in Collections:B.Tech. Project Reports

Files in This Item:
File Description SizeFormat 
Zopstore Web App Built using Three Layered Architecture.pdf1.47 MBAdobe PDFView/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.