Software Architecture: Difference between revisions
| Line 62: | Line 62: | ||
<font color=darkkhaki>Referred by: | <font color=darkkhaki>Referred by: | ||
* [[Infrastructure_as_Code_Concepts#Infrastructure_Code_Management|Infrastructure as Code Concepts | Infrastructure Code Management]]</font> | * [[Infrastructure_as_Code_Concepts#Infrastructure_Code_Management|Infrastructure as Code Concepts | Infrastructure Code Management]]</font> | ||
===Connascence=== | |||
{{Internal|Connascence|Connascence}} | |||
=Organizatorium= | =Organizatorium= | ||
Revision as of 21:08, 9 July 2023
External
- https://www.amazon.com/Clean-Architecture-Craftsmans-Software-Structure-ebook-dp-B075LRM681/dp/B075LRM681/
- Generic Development and Architecture http://www.infoq.com/articles/CCC-Jimmy-Nilsson
- Pimp My Architecture - Rearchitecting an Application without Rewriting it from Scratch http://www.infoq.com/presentations/north-pimp-my-architecture
- http://www.oodesign.com/design-principles.html
Internal
- Software Engineering
- Building Evolutionary Architectures: Automated Software Governance 2nd Edition by Neal Ford, Rebecca Parsons, Patrick Kua, Pramod Sadalage
Overview
The art of software architecture belongs under the larger domain of software engineering, alongside software development.
Subjects
- Hexagonal Architecture
- The Law of Demeter
- 12 Factor App
- Design Patterns
- Actor Model
- SOLID Principles
- Reactive Programming
- Parallelism
- Real-Time Computing
- Eventually Consistent Systems
- Fluent Interface
- Universal Scalability Law, Amdahl Law
- Domain-Driven Design
- Single Page Application (SPA)
- Self-Contained Systems
- Distributed Systems
- Software Security
- ACID
- Microservices Architecture
Concepts
Software Architecture
Evolutionary Software Architecture
Evolutionary software architecture is the sum of software engineering practices and techniques, as well as structural architectural patterns that allow incremental guided change across multiple dimensions of a software system. The dimensions in question include first and foremost the domain, but also multiple other architectural characteristics the system designers deem as important.
Requirements
Functional requirements (related to domain) and non-functional requirements, associated to architectural characteristics.
Domain
Architectural Characteristics
Framework
Platform
Architectural Governance
Definition. TO DO.
Architectural governance includes code reviews, architecture review boards (manual, bureaucracy).
Change
Incremental change.
Architectural Patterns
Coupling and Cohesion
Referred by:
Connascence
Organizatorium
- https://www.infoq.com/presentations/starling-bank: "If you develop, you break things", the story of a bank building their systems on Java. They move money. Apparently they move fast. Self-contained systems, microliths, AWS working well for them, no startup dependencies, no distributed transactions, L.O.A.S.C.T.T.D.I.T.T.E.O, shortened to DITTO, idempotency, building skepticism into services, why Java, safe instance termination.
- Next Architecture: https://www.oreilly.com/ideas/3-emerging-trends-tech-leaders-should-watch#next-architecture
- Banking startup that uses Java, deploys on AWS, and builds "microliths" https://www.infoq.com/podcasts/cloud-based-banking-startup-java
- Architectural Decision Records
- Behavior-Driven Development