EventEase Database & Web Application Design

Part 1- Project Foundation and Initial Deployment

Practically

Design and create a Basic Database Structure.

Implement ASP.NE core MVC Basics.

Integrate Azure SQL Database with ASP.NET Core.

• Deploy an ASP.NET Core web application to Azure.

Theoretically

Explain the difference between deploying on-premises and in the cloud
Identify key differences between Azure hosting models.
A. Design the EventEase Database

Based on the background information provided earlier, develop an Entity-Relationship-Diagram with an accompanying Database Script that will hold the data to be captured into the EventEase system. Your database should contain three main tables for now, based on the CEO's requirements in the background provided above.

B. Develop the Web Application

Build an ASP.NET core web application with corresponding models, controllers, and views for the EventEase system.



Your web application should include the following:

The relevant Models, Controllers and Views for each of the Venues, Events and Bookings.
Your application should communicate with your database implementing CRUD functionality.
For the images, use placeholder URLs (links to sample images) for venues and events in this phase.


Deploy your Web app and Database to Microsoft Azure:
Set up an Azure web app service and deploy your web app to this service.
Set up an Azure SQL Database and migrate your local data to the database service.
Cloud Computing Basics

1. In what ways does deploying an application in the cloud differ from deploying it on-premises,

particularly regarding security, deployment speed, and resource management? Use examples to illustrate your points.



2.What are the key differences between Infrastructure as a Service (laaS), Platform as a Service
(PaaS), and Software as a Service (SaaS), and why might EventEase benefit from the use of PaaS over the other two when building a new application? Use examples to support your
answer.

Submission Notes

Ensure all the relevant material is present in your submission i.e. your locally developed web
app, ERD, Database Script, Word document etc.
Do not forget to provide any relevant URLs such as the web app URL.
Remember that this submission must include code attribution and traditional referencing as it
includes both practical and theoretical content.