Software Architecture: Difference between revisions
Jump to navigation
Jump to search
| Line 44: | Line 44: | ||
==Architectural Patterns== | ==Architectural Patterns== | ||
==Coupling and Cohesion== | ==Coupling and Cohesion== | ||
<font color=darkkhaki>Referred by: | |||
* [[Infrastructure_as_Code_Concepts#Infrastructure_Code_Management|Infrastructure as Code Concepts | Infrastructure Code Management]]</font> | |||
=Organizatorium= | =Organizatorium= | ||
Revision as of 22:38, 1 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
Framework
Platform
Architectural Governance
Change
Architectural Characteristics
Architectural Patterns
Coupling and Cohesion
Referred by:
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