What is the difference between Façade and Mediator?
- Façade and Mediator are the same thing.
- Façade and Mediator have no relationship to each other.
- Façade is a pattern for communication between components of a system, while Mediator is a simplified interface to a complex system. Façade is a two-way communication pattern, while Mediator is a one-way communication pattern.
- Façade is a simplified interface to a complex system, while Mediator is a pattern for communication between components of a system. Façade is a one-way communication pattern, while Mediator is a two-way communication pattern.
The Façade pattern provides a simplified interface to a complex system, while the Mediator pattern provides a way for components of a system to communicate with each other in a loosely coupled manner. Façade is a one-way communication pattern, while Mediator is a two-way communication pattern.
What is the purpose of the Facade pattern?
- To allow multiple objects to communicate with each other
- To create a reusable object-oriented design
- To provide a common interface for a group of related classes
- To provide a simplified interface to a complex system, hiding the complexity of the system behind a single interface and making it easier to use
The Facade pattern provides a simplified interface to a complex system, hiding the complexity of the system behind a single interface and making it easier to use
What is the Null Object pattern?
- A creational design pattern that provides a way to instantiate an object in a superclass, but allow subclasses to alter the type of objects that will be created.
- A design pattern used to ensure a class has only one instance, while providing a global access point to this instance for the entire system.
- A software design pattern that enables an object to be passed around as a value.
- The Null Object pattern is a behavioral design pattern that provides a default object as a representative of "null" in the context of design patterns.
The Null Object pattern is a behavioral design pattern that provides a default object as a representative of "null" in the context of design patterns.
What is Command pattern?
- A design pattern that converts a request into a standalone object, allowing the client to parametrize objects with different requests, queue a request, or log requests
- A design pattern that passes a request through a chain of objects, allowing the objects in the chain to either handle the request or pass it on to the next object in the chain
- A design pattern that provides a simplified interface to a complex system, allowing the client to interact with the system through a single, unified interface
- A design pattern that uses shared objects to support large numbers of similar objects efficiently
Command pattern is a design pattern that converts a request into a standalone object, allowing the client to parametrize objects with different requests, queue a request, or log requests. The pattern involves creating a command class that encapsulates the request as an object, and passes the request to the invoker object. The invoker object then executes the command. This pattern can be useful in situations where you want to decouple the client from the receiver of the request, and where you want to provide a unified interface for undo and redo operations.
What is the difference between the State and Strategy patterns?
- None of the above
- The State and Strategy patterns are the same
- The State pattern allows an object to alter its behavior when its internal state changes, while the Strategy pattern allows an object to change its behavior based on the context it is in
- The State pattern allows an object to change its behavior based on the context it is in, while the Strategy pattern allows an object to alter its behavior when its internal state changes
The State pattern allows an object to alter its behavior when its internal state changes, while the Strategy pattern allows an object to change its behavior based on the context it is in
What is the Visitor pattern?
- A behavioral design pattern that lets you pass requests along a dynamic chain of receivers until one of them handles it.
- A behavioral design pattern that separates an algorithm from an object structure on which it operates. The pattern allows you to define a new operation without changing the classes of the objects on which it operates.
- A creational design pattern that uses factory methods to deal with the problem of creating objects without specifying the exact class of object that will be created.
- A structural design pattern that allows you to compose objects into tree structures to represent part-whole hierarchies.
A behavioral design pattern that separates an algorithm from an object structure on which it operates. The pattern allows you to define a new operation without changing the classes of the objects on which it operates.
What is Inversion of Control?
- A mechanism for managing dependencies between software components, such as libraries or services, that are required to run an application.
- A method of testing in which dependencies are replaced with mock objects to isolate the test subject from the rest of the system.
- A software design principle in which the flow of control of a system is inverted compared to the traditional approach. Instead of the system calling a component to perform a task, the component is notified when a task is ready and performs it. This leads to a more flexible and decoupled system, allowing for easier maintenance and testing.
- A technique for structuring software components into a tree-like hierarchy to organize dependencies and reduce coupling between components.
Inversion of Control is a design principle in which the flow of control in a system is inverted. Instead of a system calling components to perform tasks, components are notified when tasks are ready and perform them. This leads to a more flexible and decoupled system, allowing for easier maintenance and testing.
Name the actor classes used in Memento pattern.
- Caretaker, Originator, Memento
- Memento, Caretaker, Originator
- Originator, Caretaker, Memento
- Originator, Memento, Caretaker
The actor classes used in the Memento pattern are: Originator, Memento, and Caretaker. The Originator class is responsible for creating the memento and restoring its state. The Memento class is responsible for storing the internal state of the Originator. The Caretaker class is responsible for maintaining a list of mementos and providing the Originator with the appropriate memento at the appropriate time.
Give an example where Interpreter pattern is used?
- Interpreter pattern is used in compilers, where expressions in a programming language need to be parsed and evaluated
- Interpreter pattern is used in database management systems, where SQL queries need to be interpreted and executed
- Interpreter pattern is used in game engines, where game rules need to be interpreted and executed
- Interpreter pattern is used in web applications, where user requests need to be interpreted and processed
One example of where Interpreter pattern is used is in compilers, where expressions in a programming language need to be parsed and evaluated. The Interpreter pattern can be used to evaluate the syntax and semantics of a programming language, and generate code or perform other actions based on the results of the evaluation.
What is the Command and Query Responsibility Segregation (CQRS) Pattern?
- A pattern in which read and write operations are separated into separate models.
- A pattern that helps to avoid race conditions and deadlocks in multithreaded applications.
- A pattern used to implement inter-process communication.
- A pattern used to improve database performance by caching results in memory.
CQRS is a pattern that separates the responsibilities of querying data (read) from modifying data (write) into separate models, improving scalability and maintainability of the application.