There are always trade offsAchieve least worst architecture Characteristics <ul><li>Availability </li><li>Reliability </li><li>Testability </li><li>Scalability </li><li>Security</li><li>Agility </li><li>Fault tolerance </li><li>Elasticity</li><li>Recoverability </li><li>Performance</li><li>Deployability</li><li>Learn ability</li></ul>

First Law Of Software Architecture

Architecture partitioning <ul><li>Technical / Layered (all repositories, models, controllers in separate folders) </li><li>Domain / Modular (logic is organised by feature, sliced across models, controllers, repositories) </li></ul>Conway law<ul><li>Organisations are constrained to produce designs which are copies of communication structures of these organisations </li></ul>Component Design<ul><li>Action/actors approach </li><li>Event storming - relies on messages </li><li>Work flow approach </li></ul>Architecture style<ul><li>Monolithic</li></ul><ol><li>Layered</li><li>Pipeline </li><li>Microkernel</li></ol><ul><li>Distributed </li></ul><ol><li>Service based</li><li>Event driven</li><li>Space based</li><li>Service oriented</li><li>Microservices </li></ol>

Identifying Architecture Characteristics 

When considering distributed architecture <ol><li>Network is not always reliable </li><li>Latency is never zero </li><li>Bandwidth is not infinite</li><li>Transport cost is not zero</li><li>Network not always secure </li></ol>

Architecture Fallacies 

1. Layered / N tiered architecture<ul><li>Components are organised into logical horizontal layers (eg. Presentation layer, business layer, persistence layer, database)</li></ul>Pros<ul><li>Good for small simple apps or Web sites where budget is tight and time is short</li></ul>Cons<ul><li>Deployability, Low elasticity and scalability</li></ul>2. Pipeline Architecture <ul><li>Eg. Filter pipe Filter pipe</li><li>Pipes form the communication channel, is unidirectional, point to point</li><li>Filters - producer, transformer, tester, consumer</li></ul>3. Micro kernel Architecture Product based applications (packaged for installation on consumer) Core system and Plug in components

Monolithic Architecture

1. Service based architecture<ul><li>Partitioned/driven by domain</li><li>Some UI, independent domain services, monolithic database (or multiple)</li><li>If shared db, then use shared library for database entity objects</li></ul>2. Event driven<ul><li>Asynchronous, highly scalable, high performance</li><li>Mediator topology</li><li>Broker topology - rabbitMQ, no need Central event orchestration </li></ul>

Distributed Architecture 

Although salary surveys worldwide regularly identify software architect as one of the top ten best jobs, no decent guides exist to help developers become architects. Until now. This practical guide provides the first comprehensive overview of software architecture's many aspects. You'll examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics. Authors Neal Ford and Mark Richards help you learn through examples in a variety of popular programming languages, such as Java, C#, JavaScript, and others. You'll focus on architecture principles with examples that apply across all technology stacks.

books

Books

Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real guide exists to help developers become architects. Until now. This book provides the first comprehensive overview of software architecture's many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics.Mark Richards and Neal Ford--hands-on practitioners who have taught software architecture classes professionally for years--focus on architecture principles that apply across all technology stacks. You'll explore software architecture in a modern light, taking into account all the innovations of the past decade.This book examines: <ul><li>Architecture patterns: The technical basis for many architectural decisions</li><li>Components: Identification, coupling, cohesion, partitioning, and granularity</li><li>Soft skills: Effective team management, meetings, negotiation, presentations, and more</li><li>Modernity: Engineering practices and operational approaches that have changed radically in the past few years</li><li>Architecture as an engineering discipline: Repeatable results, metrics, and concrete valuations that add rigor to software architecture</li></ul>

Mark Richards

Neal Ford

Fundamentals of Software Architecture

﻿Shut your mouth﻿Exhale longer﻿Chew more﻿Breathe more on occasion r﻿Hold your breath

Tldr

1. Mouth Breathing only experiment was detrimental to health - increased BP, heart rate, sleep apnoea 2. Nose breathing has many health advantages

Importance Of Nose Breathing 

Compared to traditional foods, modern foods have two key differences that cause our faces to narrow, teeth to crowd and mouths to be smaller and less adapted for breathing well1. Lack of vitamins2. Softness of food, causing us to chew less<ul><li>Chewing signals stem cells to build more maxilla bone, triggering more bone density and growth, making us breathe better and look younger </li></ul>

Industrialised Food Caused Mankind's Downfall 

<ul><li>Reasons why we don't breathe well - we have small mouths</li><li>Braces/extraction makes a smaller mouth even smaller</li><li>Mike Mew's mewing tongue exercises </li><li>Importance of a bigger mouth - evidence in the perfect teeth in our forefathers </li></ul>

Nose And Mouth And Posture

<ul><li>Wim Hof heavy breathing </li><li>Holding your breath </li><li>Rama exhalation </li><li>And more.. </li><li><a href="https://www.mrjamesnestor.com/breathing-videos">Instructional Videos </a></li></ul>

Breathing Techniques

A New York Times Bestseller A Washington Post Notable Nonfiction Book of 2020 Named a Best Book of 2020 by NPR “A fascinating scientific, cultural, spiritual and evolutionary history of the way humans breathe—and how we’ve all been doing it wrong for a long, long time.” —Elizabeth Gilbert, author of Big Magic and Eat Pray Love No matter what you eat, how much you exercise, how skinny or young or wise you are, none of it matters if you’re not breathing properly. There is nothing more essential to our health and well-being than breathing: take air in, let it out, repeat twenty-five thousand times a day. Yet, as a species, humans have lost the ability to breathe correctly, with grave consequences. Journalist James Nestor travels the world to figure out what went wrong and how to fix it. The answers aren’t found in pulmonology labs, as we might expect, but in the muddy digs of ancient burial sites, secret Soviet facilities, New Jersey choir schools, and the smoggy streets of São Paulo. Nestor tracks down men and women exploring the hidden science behind ancient breathing practices like Pranayama, Sudarshan Kriya, and Tummo and teams up with pulmonary tinkerers to scientifically test long-held beliefs about how we breathe. Modern research is showing us that making even slight adjustments to the way we inhale and exhale can jump-start athletic performance; rejuvenate internal organs; halt snoring, asthma, and autoimmune disease; and even straighten scoliotic spines. None of this should be possible, and yet it is. Drawing on thousands of years of medical texts and recent cutting-edge studies in pulmonology, psychology, biochemistry, and human physiology, Breath turns the conventional wisdom of what we thought we knew about our most basic biological function on its head. You will never breathe the same again.

A New York Times Bestseller A Washington Post Notable Nonfiction Book of 2020 Named a Best Book of 2020 by NPR   “A fascinating scientific, cultural, spiritual and evolutionary history of the way humans breathe—and how we’ve all been doing it wrong for a long, long time.” —Elizabeth Gilbert, author of Big Magic and Eat Pray Love No matter what you eat, how much you exercise, how skinny or young or wise you are, none of it matters if you’re not breathing properly. There is nothing more essential to our health and well-being than breathing: take air in, let it out, repeat twenty-five thousand times a day. Yet, as a species, humans have lost the ability to breathe correctly, with grave consequences. Journalist James Nestor travels the world to figure out what went wrong and how to fix it. The answers aren’t found in pulmonology labs, as we might expect, but in the muddy digs of ancient burial sites, secret Soviet facilities, New Jersey choir schools, and the smoggy streets of São Paulo. Nestor tracks down men and women exploring the hidden science behind ancient breathing practices like Pranayama, Sudarshan Kriya, and Tummo and teams up with pulmonary tinkerers to scientifically test long-held beliefs about how we breathe. Modern research is showing us that making even slight adjustments to the way we inhale and exhale can jump-start athletic performance; rejuvenate internal organs; halt snoring, asthma, and autoimmune disease; and even straighten scoliotic spines. None of this should be possible, and yet it is. Drawing on thousands of years of medical texts and recent cutting-edge studies in pulmonology, psychology, biochemistry, and human physiology, Breath turns the conventional wisdom of what we thought we knew about our most basic biological function on its head. You will never breathe the same again.

James Nestor is a journalist who has written for Outside magazine, Men's Journal, Scientific American, Dwell, National Public Radio, The New York Times, The Atlantic, the San Francisco Chronicle, and others.

James Nestor

Breath

Reduced duplication, high expressiveness and early building of simple abstractions. That's what makes clean code for me.

Clean Code

<ul><li>﻿Use intention revealing names (elapsedTimeInDays vs d) </li><li>Class names should contain nouns and not verbs. Avoid Manager, Processor, Data, Info in class names. </li><li>Method names should have verbs. Accessory, mutators and predicates should be named for their values and prefixed with get, set, is</li><li>Use searchable names</li><li>Make meaningful distinctions</li></ul>

Ch2. Meaningful Names

Looks at the principles and clean code, includes case studies showcasing the practices of writing clean code, and contains a list of heuristics and "smells" accumulated from the process of writing clean code.

Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer--but only if you work at it. What kind of work will you be doing? You'll be reading code--lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code--of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding <ul> <li>How to tell the difference between good and bad code</li> <li>How to write good code and how to transform bad code into good code</li> <li>How to create good names, good functions, good objects, and good classes</li> <li>How to format code for maximum readability</li> <li>How to implement complete error handling without obscuring code logic</li> <li>How to unit test and practice test-driven development</li> </ul> This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

Robert Cecil Martin, commonly called Uncle Bob, is a software engineer, advocate of Agile development methods, and President of Object Mentor Inc. Martin and his team of software consultants use Object-Oriented Design, Patterns, UML, Agile Methodologies, and eXtreme Programming with worldwide clients.He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at international conferences and trade shows.

Fundamentals of Software Architecture

Breath

Clean Code

hei you