Design Patterns & Architecture Styles — SeniorA senior-level interview bank on software design patterns (GoF and enterprise), design principles, Domain-Driven Design, and the architectural trade-offs between monoliths, modular monoliths and microservices — including migration and distributed-data patterns.Price: US$ 24.89. 100 published questions in this package.Objectives

Creational Patterns

Structural Patterns

Design Principles & Anti-patterns

Behavioral Patterns

Enterprise & Application Patterns

Domain-Driven Design

Distributed Data & Integration Patterns

Monolith & Modular Monolith

Migration & Evolution

Microservices Trade-offs

SyllabusCreational PatternsStructural PatternsDesign Principles & Anti-patternsBehavioral PatternsEnterprise & Application PatternsDomain-Driven DesignDistributed Data & Integration PatternsMonolith & Modular MonolithMigration & EvolutionMicroservices Trade-offsSample questions

A teammate proposes a classic `static Instance` Singleton for a `PricingConfiguration` class used across a service. Why do many senior engineers push back on that, and what do you use instead in an application that already has a DI container?

Explain the difference between Factory Method and Abstract Factory using a concrete scenario, such as a system that must send notifications through different channels and also build channel-specific templates and delivery receipts. When is either one overkill?

When is the Builder pattern worth using compared to a constructor with many parameters, object initializers, or C# `record` types with `with` expressions? Give an example where you would not use it.

To buy and practice you need to enable JavaScript and create an account.