Mathias Paulenko

Reuse expensive objects instead of creating and destroying them repeatedly. A creational pattern for managing scarce resources efficiently.

Reliably publish domain events by persisting them in an outbox table within the same database transaction as the business operation.

Use a dedicated controller object for each logical page in a web application, handling the request and populating the view for that...

Split a single class definition across multiple source files to separate auto-generated code from hand-written code, or to organize large...

Enable third-party extensions by defining extension points in a host system that loads and executes live external modules.

Process tasks based on priority rather than arrival order, ensuring high-priority work gets resources before lower-priority tasks even if...

Introduce a queue between task producers and consumers to smooth out traffic spikes, decouple components, and prevent downstream services...

Centralize access to shared services and objects via a lookup table. A structural pattern that decouples consumers from concrete...

Assign dynamic roles to objects at runtime instead of hard-coding behavior in class hierarchies, enabling flexible identity changes without...

Coordinate resilient job scheduling by separating scheduling logic from execution agents and adding a supervisor that monitors, restarts,...

Encapsulate business rules for selecting objects as reusable, composable predicate objects that can be combined with logical operators.

Provide an alternative to multiple inheritance by linking two separate classes through mutual references, allowing them to delegate methods...

Define game object types as runtime data rather than hard-coding them as classes, enabling designers to create new entity variants without...

Track changes to in-memory objects during a business transaction and commit all updates atomically to the database, ensuring consistency.

Model domain concepts by value rather than identity. An immutable object defined by its attributes, not by a unique ID.

A practical guide to combining CQRS and Event Sourcing: separating read and write models, rebuilding state from events, and handling...

A practical guide to Data Lake architecture: structured vs unstructured storage, lakehouse concepts, ETL vs ELT patterns, and when to...

A practical guide to Data Mesh: decentralizing data ownership to domain teams, treating data as a product, and enabling self-serve data...

A practical guide to Lakehouse architecture: combining data lake storage flexibility with data warehouse reliability using open table...

A practical guide to Layered (N-Tier) Architecture: separating presentation, business logic, and data layers with clear responsibilities...

A practical guide to Onion Architecture: organizing code around the domain model, enforcing dependency direction inward, and isolating...

A practical guide to serverless architecture: function design, cold starts, event-driven patterns, state management, and common pitfalls...

A practical guide to Vertical Slice Architecture: organizing code by feature instead of technical concern, reducing cross-layer navigation...

A practical guide to cloud blob storage: bucket design, access control, lifecycle policies, multipart uploads, presigned URLs, and cost...