Software Architecture: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
=Internal= | =Internal= | ||
* [[Software Engineering]] | * [[Software Engineering]] | ||
=Subjects= | =Subjects= | ||
Revision as of 01:26, 17 September 2021
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
TODO
- Clean Architecture https://www.amazon.com/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164/
Internal
Subjects
- Hexagonal Architecture
- The Law of Demeter
- 12 Factor App
- Blue-Green Deployment
- Don't Repeat Yourself (DRY)
- Design Patterns
- Actor Model
- SOLID Principles
- Reactive Programming
- Parallelism
- Real-Time Computing
- Eventually Consistent Systems
- Stream Processing
- Fluent Interface
- Universal Scalability Law, Amdahl Law
- Conway's Law
- Domain-Driven Design
- Single Page Application (SPA)
- Self-Contained Systems
- Distributed Systems
- Software Security
- Cohesion
- Coupling
- ACID
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