Skip to content
#Patterns

2. The Patterns - and here are the patterns for solving standard problems from the areas discussed in the first part

#Patterns #Software #SoftwareArchitecture #SoftwareDevelopment #Architecture #SystemDesign
  • Domain Logic Patterns This is a transaction script. (for simple business logic)Domain model, table module, service layer, which we discussed above
  • Data Source Architectural Patterns Table data gateway, row data gateway, active record data mapper
  • Object-Relational Behavioral Patterns Behavioral patterns: unit of work, identity map, lazy load
  • Object-Relational Structural Patterns There are many structural patterns, many of which are related to data, identity field, foreign key mapping, association table mapping, dependent mapping, embedded value, serialized LOB. As well as a set of patterns for solving the problem of storing information about inheritance hierarchies in a relational database: single table inheritance, class table inheritance, concrete table inheritance, inheritance mappers.
  • Object-Relational Metadata Mapping Patterns - Patterns for storing metadata about the relationship of classes and entities in the database: metadata mapping, query object, repository
  • Web Presentation Patterns - a lot of patterns about representation, but from practice that was relevant 20 Model view controller, page controller, front controller, template view, transform view, two step view, application controller. If you read this, it’s for historical reasons:)
  • Distribution Patterns There are only two patterns for solving the problem of distributed objects: remote facade, DTO. (data transfer object)
  • Offline Concurrency Patterns Patterns for working with competition: optimistic offline lock, pessimistic offline lock, coarse-grained lock, implicit lock
  • Session State Patterns Patterns of relative storage of the client session state: client session state, server session state, database session state
  • Base Patterns are basic patterns that do not fall into other categories: gateway, mapper, layer supertype, separated interface, registry, value object, money, special case, plugin, service stub, record set. These patterns are quite simple and are often used in different scenarios.

Anyway, a book for 2002 The year was just a fire - she talked about approaches to design and solving typical problems. The Martin Fowler Signature series has also produced other books that explore the subject. Book Review: Enterprise Integration Patterns (Templates for integration of corporate applications)"that I mean." told earlier. Well, now the book is rather a base that many study from other books that came out later and talk about current patterns in the context of a particular platform. (Java, Kotlin, .Net, Python, ...) And they make it super accessible.

#Patterns #Software #SoftwareArchitecture #SoftwareDevelopment #Architecture #SystemDesign