Technical University of Munich [IN2081]
Patterns in Software Engineering (Exam)
<aside>
<aside>
✅ - done, ❌ - todo, 🔄 - in process
Week 0.0✅ (Basics of UML and SE) Week 0✅ Repetition I (Composite, Facade, Bridge, Proxy, Adapter) Week 1✅ Introduction (Software Engineering) Week 2✅ Repetition II (Observer, Strategy, REST, Layered, Mock) Week 3✅ Design Patterns I (State, Template, Command, Mediator) Week 4✅ Design Patterns II (Factory, Abstract, Flyweight, Builder) Week 5✅ Architectural Patterns I (MVC, Broker, AI Agent) Week 6✅ Architectural Patterns II (REST, gRPC, Microservices) Week 7✅ Antipatterns I (Golden Hammer, Lava Flow, The Blob, Functional Decomposition) Week 8✅ Antipatterns II (Spaghetti Code, Ctrl+C & Ctlr+V, Vendor lock-in, Analysis Paralysis, Refactoring) Week 9✅ Testing Patterns I (EasyMock, Mockito, Reflection Test, Testing MVC) Week 10✅ Testing Patterns II (Dependency Injection with Guice, Spring, REST Testing) Week 11✅ Microservice Patterns I (Strangler, Decentralized, Circuit Breaker, Async Messages) Week 12✅ Microservice Patterns II (Blue-Green, Canary, Feature Toggles, Retry)
<aside>
<aside>
please use this comment section →

</aside>
What do you have to do to kill a project?

Creational Design patterns provide various object creation mechanisms, which increase flexibility and reuse of existing code
<aside>
Design Patterns
</aside>