Skip to content

Latest commit

 

History

History
63 lines (46 loc) · 2.65 KB

File metadata and controls

63 lines (46 loc) · 2.65 KB

Week 0 — Billing and Architecture

Architecture

A good requirement is to be measurable and specific, which will aid in understanding in the long run.

  • verifiable
  • monitor able
  • traceable
  • feasible

It's important to keep risks, assumptions, and constraints in mind.

Risks examples:

  • User commitment, late deliveries.
  • single point of failure.
  • Assumptions are things that we pretend are true but are not.
  • budget changes,
  • stakeholders availability.
  • sufficient network bandwidth.

The technical limitations are

  • time: 14 weeks of boot camp.
  • budget – utilizing the free tier.
  • AWS vendor selection.

In the design phase, we should sketch a diagram of infrastructure.

  • There are three steps to this.
  • Conceptual design is an abstract idea created by stakeholders without specific details.
  • Database, Server, no specifics.

Logic Design

How it should be implemented, without actual names

Physical design

  • Represent the actual infrastructure that was built.
  • IP addresses, EC2 instances, access resource names, bucket names
  • This phase is super important.

"Dumb questions," such as "do we have enough skillsets, enough workforce?" must be asked.

Document everything:

  • Where the data lies and how it works
  • Use AWS's well-architected framework to review your workloads against current AWS best practices. The main idea is to ask the right questions without getting too caught up in infrastructure.
  • Knowing the AWS well-architected framework allows you to ask stakeholders and engineers the right questions.
  • It's good to ask what the goal of this meeting is, especially if they have different backgrounds. Try to overcome your fear of asking "dumb questions" and ask about architecture.

Insights

Security

Architecture design

Sharing Conceptual and Logic diagrams. Conceptual diagram was draw on real napkin, picture uploaded to repo. Conceptual design on napkin

Logical diagram

https://lucid.app/lucidchart/46cad15b-f4eb-4a9e-a88f-4608e524253a/edit?viewport_loc=-1470%2C-1148%2C3234%2C1576%2C9o6y40-67mdX&invitationId=inv_187a3bf1-f0b3-4fbc-8883-7d85df761478