Design pattern
A reusable solution structure for a recurring software design problem, with its own trade-offs.
What is a design pattern?
A design pattern describes a reusable solution structure for a recurring software design problem. It explains an approach together with conditions for use and drawbacks. It is neither a finished product nor code that can be copied unchanged into every project. Suitability depends on the particular problem.
In a fictional modernisation project, an adapter layer translates between the request models of an old and a new application. This can shield the new part from peculiarities of the old model. Meanings still need clarification: renaming a field does not resolve conflicting business rules. The additional translation brings maintenance work and its own failure cases. A pattern should therefore address a named need rather than merely increase the number of patterns in use.
Sources
Related terms
- Software architectureFundamental decisions about a software system’s structure, interactions and quality goals.
- Clean ArchitectureSeparating business rules from external details and directing source-code dependencies towards the core.
- Cache stampedeA cache stampede occurs when concurrent cache misses trigger the same expensive calculation or data query repeatedly.
- BackpressureBackpressure adjusts incoming data to the receiver’s processing capacity through signals to slow down or pause.
- Race conditionA result depends on the timing of overlapping accesses and can therefore be wrong.
- Memory leakMemory that is no longer needed stays allocated while the program runs.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.