Seonglae ChoOrganize layers hierarchically while reducing module dependencies (coupling) and increasing code cohesion
Spaghetti Code: No code layer & consistency, complex dependency
Rather than developing linearly in response to ad-hoc requests, it's much faster in the long run to pursue accelerated development through structural design, even if it delays immediate development. An ideal step-function progress graph that continuously presents new structures is optimal
- Cohesion - Similar code with related responsibilities should be grouped together
- Coupling - Modifying one feature should require changes to only one piece of code
Flexibility over time determines where design concepts should live. What changes frequently belongs in the data, while the schema of the data should fix the standard of what never changes. Code changes more easily than schema but less easily than data. UI is easy to change but not as easy as data.
Software Architectures
ย
ย
Software Architecture Notion
ย
ย
ย
One thing that should be learned from the Bitter Lesson is the great power of general-purpose methods, of methods that continue to scale with increased computation even as the available computation becomes very great. - Richard Sutton
ย
ย
Unlike the subjective nature of "Easiness" and "Hardness," "Simplicity" and "Complexity" are objective concepts. "Simple" refers to an uncomplicated, one-fold structure, while "complex" means a state where multiple layers are intertwined. Easy/Hard are relative terms, and people choosing what seems easy doesn't necessarily guarantee a simple structure.
For simplicity, instead of interleaving complex structures, separate components and then compose them to connect simple elements.
"Simple Made Easy" - Rich Hickey (2011)
Rich Hickey, the author of Clojure and designer of Datomic, is a software developer with over 30 years of experience in various domains. Rich has worked on scheduling systems, broadcast automation, audio analysis and fingerprinting, database design, yield management, exit poll systems, and machine listening, in a variety of languages.
This keynote was given at Strange Loop 2011, and is perhaps the best known and most highly regarded of Rich's many excellent talks, ushering in a new way to think about the problems of software design and the constant fight against complexity.
The video was recorded at Strange Loop in partnership with InfoQ, who have hosted it on their site since 2011. This version (released 10 years later) is a new edit made from the original HD video and slides, restoring the slide transitions and animations as it was given in 2011.
https://www.youtube.com/watch?v=SxdOUGdseq4
Hexagonal Architecture
๊ฐ์ ์ด๋ฒ ํฌ์คํ
์์๋, ์ก๊ฐํ ์ํคํ
์ฒ(Hexagonal Architecture) ์ ๋ํด์ ์์๋ณด๊ณ ๊ฐ๋จํ ์์ ๋ฅผ ํตํด ์ค์ ๋ก ์ด๋ป๊ฒ ์ก๊ฐํ ์ํคํ
์ฒ๋ฅผ ์ ์ฉ ํ๋์ง์ ๋ํด์๋ ์์๋ณด๋๋ก ํ๊ฒ ์ต๋๋ค. ๊ณ์ธตํ ์๋ ์ฝ๋ = ์คํ๊ฒํฐ ๋จผ์ ์ก๊ฐํ ์ํคํ
์ฒ๋ฅผ ์ค๋ช
ํ๊ธฐ ์ ์, ์ ๊ฐ ์ฒซ ํ๋ก์ ํธ๋ฅผ ์งํํ์๋์ ์ด์ผ๊ธฐ๋ฅผ ํด๋ณด๊ฒ ์ต๋๋ค. ์ ๊ฐ ๋ชจ ๊ธฐ๊ด์์ ์๋๋ก์ด๋ APK ๋ณด์์ทจ์ฝ์ ๋ถ์์ ์ํํด์ฃผ๋ ์๋น์ค๋ฅผ ์งํํ์๋, ์ ๋ ๋ชจ๋ํ๋
https://blog.imqa.io/hexagonal-architecture/
ย
ย
ย