Belosan's CIS411_LAB1

labreports/LAB_[belosanj].md

@@ -0,0 +1,94 @@
+# Lab Report Template for CIS411_Lab1
+Course: Messiah College CIS 411, Spring 2020
+
+Instructors: [Joel Worrall](https://github.com/tangollama) & [Trevor Bunch](https://github.com/trevordbunch)
+
+Name: Belosan Jekale
+
+GitHub: [belosanj](https://github.com/belosanj)
+(if appropriate) Collaborators: [Names of colleagues you worked with on this assignment]
+
+
+# Step 0: Reviewing Architectural Patterns
+See the [lecture / discussion](https://docs.google.com/presentation/d/1nUcy63FWPFYO3OJmERJpMjEtdaFtaIBbuUkpmNRVRas/edit#slide=id.g45345bd5ea_0_136) from CIS 411. You'll need to be familiar with the content from this lecture to complete this assignment.
+
+Note: you are free to work with classmates on this assignment. _Good architecture is born out of collaboration - not reclusive mad-scientist behavior._ However, if you work with colleagues:
+
+1. You must specifically note your collaborators by name at the top of your report.
+2. You may not completely copy each others work (diagrams and descriptions, even if your solutions are identical).
+
+# Step 1: MVC Architecture
+Review the proposals for the Serve Central project. Let's imagine that the project has been granted (relatively) unlimited resources if they can deliver a version 1 release in 120 days. As a result, the team decides to implement an MVC architecture for its version 1 release, delivering functionality through a [responsive web application](https://en.wikipedia.org/wiki/Responsive_web_design). 
+
+Based on the [this](https://docs.google.com/presentation/d/1UnU0xU0wF1l8pAB8trtLpdM0yuskx66jTFJzd64nsjU/edit#slide=id.g439b9c6866_2_53) and [this](https://docs.google.com/presentation/d/1-VZfAFoBVr6ijNepKAtRA7JoAQsV2Jlbf2l1WPDMhI0/edit) presentation:
+
+1) Document two use cases of your choosing
+
+| Use Case #1 ||
+|---|---|
+| Title |As a volunteer, I want to find volunteer opportunities in my area.|
+| Description / Steps |1. Turn location on phone or device being used 2. login to app 3. Search for volunteer opportunites |
+| Primary Actor |Volunteer|
+| Preconditions |1. Volunteer is looking for a volunteer opportunity 2. There are volunteer opportunities on database|
+| Postconditions |1. I found multiple volunteer opportunities in my area 2. I applied to the closest volunteer opportunity|
+
+| Use Case #2 ||
+|---|---|
+| Title |As a recruiter, I want to hire the best volunteer.|
+| Description / Steps |1. Look for Keywords within resume 2. Schedule interviews 3. Choose best applicant|
+| Primary Actor |Recruiter|
+| Preconditions |There are a hand full of people who applied 2. Database with all applications is available|
+| Postconditions |1. I found the best volunteer 2. I recruited the best volunteer|
+
+1) Highlight a [table](https://www.tablesgenerator.com/markdown_tables) of at least **four models, views, and controllers** needed to produce this project.
+
+| Model (data) | View (page) | Controller (initiate action)  |
+|---|---|---|
+| Volunteer | Profile View | Edit Profile |
+| Recruiter | VolunteerList View | Update volunteerList |
+| Interview | InterviewList View | Schedule interviews |
+| Event | Events View | event registration |
+
+3) Generate and [embed](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#images) at least one diagram of the interaction between an Actor from the Use Cases, and one set of Model(s), View(s), and Controller(s) from the proposed architecture, including all the related / necessary services (ex: data storage and retrieval, web servers, container tech, etc.)
+
+[Diagram interacting Use Case and MVC](asset/MVC.png)
+
+_Note: You are free to use any diagraming tool and framework that you want as long as it clearly communicates the concept. I typically use a UML System Use Case or [UML Sequence Diagram](https://www.uml-diagrams.org/index-examples.html).  If you do not have a preferred diagramming tool: [draw.io](http://draw.io) or [lucidchart](http://lucidchart.com) are good cloud-based options._
+
+# Step 2: Enhancing an Architecture
+After an initial release and a few months of operation, Serve Central encounters a tremendous growth opportunity to extend their service and provide a volunteer recuitment and management interface to __four__ of the primary volunteer entities in the United States. As such, a reevaluation of the architecture is required, one that allows:
+
+1. Thirdparty services to both input and retrieve data from the Serve Central model/datastore. (For instance, receiving volunteer opportunities from United Way chapters across the country.)
+2. Building organization-specific interfaces on top of the Serve Central business and data logic. (For instance, allowing the registration services of Serve Central to be embedded in the website of local churches, [ah-la Stripe embedding](https://stripe.com/payments/elements).)
+
+To support these objectives:
+1. What architectural patterns (either of those presented in class on based on your own research) are appropriate? Justify your response, highlighting your presumed benefits / capabilties of your chosen architecture(s) **as well as as least one potential issue / adverse consequence** of your choice.
+
+I believe that the best architectural patterns for these objectives is **Broker**. The **Benefits** for this architectural pattern is that it can make distribution transparent to developers, it can also be designed to decouple clients from servers and it connects clients with remote objects. A challenge for this pattern would be that it requires standardization of service descriptions. 
+
+2. Using your preferred diagramming tool, generate a diagram of the new Serve Central architecture that supports these two new requirements.
+
+[New Serve Central architecture](asset/Broker.png)
+
+# Step 3: Scaling an Architecture
+18 months into the future, Serve Central is experiencing profound growth in the use of the service with more than 100k daily, active users and nearly 1M event registrations per month. As a result, the [Gates Foundation](https://www.gatesfoundation.org/) has funded a project to build and launch a mobile application aimed at encouraging peer-to-peer volunteer opportunity promotion and organization. 
+
+In addition to building a new mobile application interface, the grant requires that the project prepare for the following future needs:
+
+1. Consuming bursts of 10k+ new volunteer opportunities per hour with a latency of less than 15 seconds between submitting an opportunity and it's availability in the registration service.
+2. Supporting a volunteer and event data store that will quickly exceed 50TB of data
+3. Allowing authorized parties to issue queries that traverse the TB's of data stored in your datastore(s).
+4. Enabling researchers to examine patterns of volunteer opportunities as a way of determining future grant investments.
+
+What archictural pattern(s) will you employee to support each of these needs? What will the benefits and consequences be? Why are changes needed at all? Justify your answers.
+
+The architecture patterns that I will employe to support each of these needs are **Microservices**. Since Serve Central has grown exponentially, Microservice architecture pattern works best. Serve Central is growing and having larger data therefore it Microservices are great for large/growing companies. Also when looking at Microservices, it offers smaller codebases abd scope leading to quicker depolyments. Not only is it faster it is also easier to understand and eliminates dependency on technology stack. Although there are many advantages, a challenge is that communication between services can be complex.
+
+# Extra Credit
+1. Create and embed a comprehensive diagram of your final architecture (i.e. one that meets all the requirements of this lab, including Step 3).
+
+[Final architecture](asset/Microservices.png)
+
+2. Augment/improve the assignment. Suggest meaningful changes in the assignment and highlight those changes in the extra credit portion of your lab report.
+
+A change that could be added a simplifying the communication between services.