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. 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 

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

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 

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>