Complete guide to become better architect from Udemy- Mavi

Architects MindSet - Its not about coding its about a new mindset -

Make yourself familar with organizations :

weakness strengths competition growth strategy how all systems integrate - Understand biz before working on architecture Need to know - What keeps CEO awake in nights

Define systems goal

Goals are not requirements and its not what the system should do. Goals describe the effect on the organization.

Example 1

system - hr orgarnization - product oriented company goals - streamline the recruitment process

Example 2

system - reporting and mapping criminal incidents org - large city goals - improve police response time, attract new residents

Work for your clients client

Talk to right people with a right language (to project managers - time, developers - technology, business leader - time to market)

Section 4: The Architecture Process

Introduction Understanding system requirement Understanding non function requirement Map the component select technology design architecture document support the team

Section 5 : Working with System requirement

Functional and Non functional requirements Non function requirement

Performance - Talk in numbers. 1 second, 100 ms Latency - how much time does it take to perform a single task **Throughput **- How many tasks can be performed in a given time unit? Load - Quantity of work the system can withstand without crashing? (Its about Availablity) for WebAPI - how many concurrent request without crashing?

Load vs ThroughPut

Throughput - 100 requests /sec Load - 500 request without crashing (time taken to complete a request is not much concern) always plan for extremes case.

Data Volume - how much data system will accumulate over time? Helps with deciding on Database Type, Designing queries ( table of 100 rows and 100000 is different),

2 aspects of data

Data required on Day 1? (500 mb) Data Growth (5TB)

Concurrent Users - how many users will be using system simulatansiouly?

Concurrent Users - including dead times Load - Actual requests. SLA - 99.99% =

24 * 365 = 8760 8760 * 99.99 % = 8759.12 8760 - 8759.12 = 0.88 hrs.

How many users can be saved in db ? How many files can be read in a second?

Section 11 : System Architecture