2. ORKHAN GASIMOV
Architecture Practice Coordinator,
Digital Transformation Architect,
GlobalLogic
I am a passionate digital architect working at enterprise and solution
architecture levels. I work with projects transforming existing businesses
and those aimed to create new digital products by providing guidance
and help to oversee possible issues along the journey.
I love to motivate people, I love technology, and I’m proud to take part
in development of technologies that supercharge the world. I also love
to support community by providing talks at meetups and conferences,
sharing experience at global scale.
5. THE PROCESS
Initiate
Definition and validation of initial requirements
Construct
Design
Test in small (design and code review)
Deliver
Test in Large
Rework
Assess
Maintain
Initiate
Construct
Deliver
Maintain
6. RISK MANAGEMENT
The time, scope and resources invested in performance management must be
proportional to project risks.
7. DESIGN DOCUMENT
IF YOU DON’T DOCUMENT IT,
IT DOESN’T EXIST!
• Architecture and detailed design documents
• Verification criteria of subsystem / component
• Test plan
• Test cases
• Requirements
1. Use cases
2. Budgets
3. Measurement and instrumentation
13. INSTRUMENTATION PRINCIPLE
The most basic example – Logging
Instrument your code/app to see what’s happening inside
Instruments should be able to operate in different modes
15. RESOURCE SHARING PRINCIPLE
System resources are limited
Processes compete for resources
Some resource are available for shared usage (concurrent or sequential)
1. Use resources when they are available
2. Minimize resource lock/block time and free resources asap
3. Minimize execution window for planned jobs/tasks
16. PARALLEL PROCESSING PRINCIPLE
1. Process in parallel when communication overhead is less than performance gain
2. Measure communication and resource concurrency overhead
17. LOAD SHARING PRINCIPLE
Balance the workload by handling conflicting tasks at different times or in different locations.
1. Plan processes so that they do not use resources at the same time
2. Divide resources in such a way that processes use different parts of the resource, and do
not require the entire resource
19. CENTERING PRINCIPLE
Dominant workload functions:
A subset of system functions that are frequently used (20% of functions or less) and
that are performed 80% of time or more
1. Identify the dominant workload function and minimize their processing.
2. It is necessary to design / implement the dominant functions first.
20. FIXING-POINT PRINCIPLE
The fixing point is a point in time.
The latest fixing point is during execution, just before instructions are to be executed.
For responsiveness, fixing should establish data connections at the earliest feasible
point in time, such that retaining the connection is cost-effective
21. LOCALITY PRINCIPLE
Locality – closeness of desired actions, functions, and results to the physical resources
used to produce them.
Types of locality
1. Spatial
2. Temporal (i.e., time)
3. Effectual (i.e., purpose or intent)
4. Degree (i.e., intensity or size)
22. PROCESSING VS FREQUENCY PRINCIPLE
The trade-off between
the amount of work done in processing a request
and the number of requests received.
