Update WRITEUP.md

WRITEUP.md

@@ -1,12 +1,40 @@
-# Write-up Template
+# Resource Option Analysis for CMS App
 
-### Analyze, choose, and justify the appropriate resource option for deploying the app.
+## Options Considered
+- Azure Virtual Machine (VM)
+- Azure App Service
 
-*For **both** a VM or App Service solution for the CMS app:*
-- *Analyze costs, scalability, availability, and workflow*
-- *Choose the appropriate solution (VM or App Service) for deploying the app*
-- *Justify your choice*
+## Comparison
 
-### Assess app changes that would change your decision.
+### Azure VM
+- Full control over server and OS
+- Manual setup and maintenance
+- Manual scaling
+- More management effort
+- Better for custom software needs
 
-*Detail how the app and any other needs would have to change for you to change your decision in the last section.* 
+### Azure App Service
+- Managed web hosting
+- Easy deployment from GitHub
+- Easy scaling
+- High availability
+- Less maintenance
+
+## Chosen Option: Azure App Service
+
+## Justification
+Azure App Service is the best choice for this CMS app because it is a Flask web application with SQL Database and Blob Storage. It does not need server-level customization. App Service provides faster deployment, easier scaling, better reliability, and lower management effort.
+
+## When VM Would Be Better
+A VM would be better if the app required:
+- Custom OS configuration
+- Special software/drivers
+- Background services
+- Advanced networking setup
+- Full server control
+
+## What Would Need to Change
+To move to a VM, the app would need advanced infrastructure requirements such as custom packages, continuous background tasks, or unsupported dependencies.
+
+## Conclusion
+For the current CMS project, Azure App Service is the most suitable and efficient deployment option.