Metaprogramovanie / Architektúra

Architektúra softvéru

• Štruktúra systému
• Rozhodnutia, ktoré je zložité zmeniť
• Ako umožniť odloženie nepodstatných rozhodnutí?

SOLID

• Single Responsibility Principle
• Open-Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• Dependency Inversion Principle

Single Responsibility Principle

A module should have one, and only one, reason to change.

A module should be responsible to one, and only one, actor.

Single Responsibility Principle

A module should be responsible to one, and only one, actor.

Open-Closed Principle

A software artifact should be open for extension but closed for modification.

Liskov Substitution Principle

Subtype Requirement: Let $\phi (x)$ be a property provable about objects $x$ of type $T$. Then $\phi (y)$ should be true for objects $y$ of type $S$ where $S$ is a subtype of $T$.

– Barbara Liskov

Interface Segregation Principle

• Rozhranie je pre klienta, nie pre poskytovateľa

Dependency Inversion Principle

1. High-level modules should not import anything from low-level modules. Both should depend on abstractions (e.g., interfaces).
2. Abstractions should not depend on details. Details (concrete implementations) should depend on abstractions.

Dependency Injection

• Dependency inversion principle
• Inversion of Control Containers and the Dependency Injection pattern

Spring

Spring Framework

• http://spring.io/
• Aplikačný rámec
• Zjednodušenie návrhu aplikácií
• Minimalizácia závislosti

Príklad

Dependency Injection

Kód

https://git.kpi.fei.tuke.sk/meta/examples/spring-di

Spring Data

Spring Data

• Zjednodušený prístup k dátam v rôznych úložiskách
• Generovanie prístupových tried

Príklad

Kód

https://git.kpi.fei.tuke.sk/meta/examples/spring-data

Je reflexia pomalá?

Vyskúšajme!

Kód

https://git.kpi.fei.tuke.sk/meta/examples/reflection-performance