Lesson 187 - Categorizing Architectural Characteristics

  Рет қаралды 2,644

Mark Richards

Mark Richards

Күн бұрын

Пікірлер: 16
@pftg
@pftg 5 ай бұрын
So neat introduction to the categories! ❤❤❤ There is only one bias suggestion, which presents in all videos 😊 Mark's comparison of testing microservices versus monoliths is flawed. Transitioning from monoliths to microservices makes testing more challenging due to network connections and other integration complexities. Testing a single unit of a monolith should require the same amount of effort or less compared to one testing microservice unit, as the functions are the same but without the overheads.
@markrichards5014
@markrichards5014 5 ай бұрын
You are correct - the more services talk to each other the harder it is to test. However, a microservice has a much smaller testing scope than a monolith does, allowing for more completeness (and ease) of testing. For example, running 23 test cases for a microservice is much easier (and faster) than running several thousand test cases within a monolithic system.
@pftg
@pftg 5 ай бұрын
⁠@@markrichards5014Thank you for responding to my comment. I would appreciate it if you could share some references or direct me to your previous videos so I can learn more about the topic. I'm still a bit unclear and would like to clarify it. When dealing with 2 components, A and B, creating integration tests that cover their collaboration is essential. These test suites are required for both monolith and microservices architectures. And it's not just a unit test to one component, but integration for the whole system.
@sant4398
@sant4398 5 ай бұрын
Thanks for new lesson! Portability looks for me like an Operational AC, while Interoperability can be also considered as a Process AC. Am I missing something? )
@markrichards5014
@markrichards5014 5 ай бұрын
No, you aren't missing anything. No categorization is perfect, and there is some cross-over. I chose to put portability and interoperability into the structure category just because those characteristics are influenced most by the structure of the system, and don't relate to the classic operational ones (like performance or scalability) in the same way. However, you can certainly place them in other categories as you see fit.
@ZahidAnsari-ER-91
@ZahidAnsari-ER-91 5 ай бұрын
Happy to inform that yours truly has bought Fundamentals of Software Architecture yesterday.
@markrichards5014
@markrichards5014 5 ай бұрын
Thanks great! Happy reading!
@mahdi5796
@mahdi5796 5 ай бұрын
Thank you. But can you please make a video and explain what's the practical benefit of these categories? How can they be used? Or they are just "nice to know"?
@sant4398
@sant4398 5 ай бұрын
+1 to the question. I have the same question.
@markrichards5014
@markrichards5014 5 ай бұрын
Great idea! I'll definitely do that. Categorization helps gain a better understanding of the different kinds of characteristics available, and also breaks down the ones you might want to consider based on your needs (process-based or operational-based)
@david56681
@david56681 5 ай бұрын
Thanks Mark, just discovered your channel, great content! Questions about security: you classify the security as structural and cross-cutting characteristic. In large companies, this is THE essential one whatever the application, so incurring costs which may be overrated for some. Do you have any framework/tips on how to "adapt" the right level for each product.
@markrichards5014
@markrichards5014 5 ай бұрын
Unfortunately I don't. It really involves a cost/benefit analysis for each part of a system or product, and a tight collaboration between the architect and the product team.
@carlosjavierbellotti6660
@carlosjavierbellotti6660 5 ай бұрын
Graeat video. Thanks for this and for share you knowledge. Can you make a video or give us some info about comparing differents aspects of operational categories that overlaps with each other? For example, in a microservice architecture, the more responsiveness your system is,, the more you will sacrifice data consistency because you provide data to other services through events instead of send the data synchronously. Thanks!!
@markrichards5014
@markrichards5014 5 ай бұрын
Sure, that's a great idea. There are many common tradeoffs, the most classic ones being availability and data integrity / consistency (CAP Theorem), and responsiveness/performance and security/access control.
@sant4398
@sant4398 5 ай бұрын
Am I only a person who hear a low frequency bump sound periodically on Mark's videos? )
@markrichards5014
@markrichards5014 5 ай бұрын
I don't hear it, but I might not have the sensitive equipment you do. I think it might be tapping my iPad as I forward the slides.
Lesson 186 - Fallacy #11: Observability is Optional
9:15
Mark Richards
Рет қаралды 2,9 М.
Lesson 102 - Architecture Characteristics FAQ
12:00
Mark Richards
Рет қаралды 3,5 М.
REAL 3D brush can draw grass Life Hack #shorts #lifehacks
00:42
MrMaximus
Рет қаралды 12 МЛН
🕊️Valera🕊️
00:34
DO$HIK
Рет қаралды 14 МЛН
小丑家的感情危机!#小丑#天使#家庭
00:15
家庭搞笑日记
Рет қаралды 36 МЛН
НАШЛА ДЕНЬГИ🙀@VERONIKAborsch
00:38
МишАня
Рет қаралды 3 МЛН
Lesson 188 - Identifying Architectural Characteristics
9:45
Mark Richards
Рет қаралды 3,3 М.
Lesson189 - Architectural Quantum Tradeoffs
13:05
Mark Richards
Рет қаралды 2,5 М.
Lesson 185 - Residuality Theory
12:17
Mark Richards
Рет қаралды 3,3 М.
Lesson 181 - Feasibility and Questioning Requirements
9:58
Mark Richards
Рет қаралды 2,9 М.
Lesson 184 - Running an Architecture Kata Session
14:43
Mark Richards
Рет қаралды 3,9 М.
Lesson 190 - Logical vs Physical Architecture
10:12
Mark Richards
Рет қаралды 4,3 М.
Lesson 195 - Sacrificial Architecture
10:38
Mark Richards
Рет қаралды 2,3 М.
Architecture A to Z [Guide to Popular Concepts]
13:36
Stewart Hicks
Рет қаралды 289 М.
Lesson194 - Architecture as Code
9:48
Mark Richards
Рет қаралды 3,2 М.
Lesson192 - Identifying Components: The Workflow Approach
7:20
Mark Richards
Рет қаралды 2,9 М.
REAL 3D brush can draw grass Life Hack #shorts #lifehacks
00:42
MrMaximus
Рет қаралды 12 МЛН