Autumn SALE
Facade

Facade を C++ で

Facade 構造に関するデザインパターンの一つで 複雑なクラスのシステム ライブラリー またはフレームワークに対して単純な しかし限定された インターフェースを提供します

Facade は アプリケーションの全体としての複雑さを軽減しますが それと同時に望ましくない依存性を一箇所に集めるのにも役立ちます

複雑度

人気度

使用例 Facade パターンは C++ のアプリでよく見かけます 複雑なライブラリーや API を相手にする時 特に役に立ちます

見つけ方 単純なインターフェースのクラスがほとんどの作業を他のクラスに委任していたら Facade パターンの使用が識別できます 通常 ファサードは それが使うオブジェクトのライフサイクルを完全に管理します

概念的な例

この例は Facade デザインパターンの構造を説明するためのものです 以下の質問に答えることを目的としています

  • どういうクラスからできているか
  • それぞれのクラスの役割は
  • パターンの要素同士はどう関係しているのか

main.cc: 概念的な例

/** * The Subsystem can accept requests either from the facade or client directly. * In any case, to the Subsystem, the Facade is yet another client, and it's not * a part of the Subsystem. */ class Subsystem1 { public: std::string Operation1() const { return "Subsystem1: Ready!\n"; } // ... std::string OperationN() const { return "Subsystem1: Go!\n"; } }; /** * Some facades can work with multiple subsystems at the same time. */ class Subsystem2 { public: std::string Operation1() const { return "Subsystem2: Get ready!\n"; } // ... std::string OperationZ() const { return "Subsystem2: Fire!\n"; } }; /** * The Facade class provides a simple interface to the complex logic of one or * several subsystems. The Facade delegates the client requests to the * appropriate objects within the subsystem. The Facade is also responsible for * managing their lifecycle. All of this shields the client from the undesired * complexity of the subsystem. */ class Facade { protected: Subsystem1 *subsystem1_; Subsystem2 *subsystem2_; /** * Depending on your application's needs, you can provide the Facade with * existing subsystem objects or force the Facade to create them on its own. */ public: /** * In this case we will delegate the memory ownership to Facade Class */ Facade( Subsystem1 *subsystem1 = nullptr, Subsystem2 *subsystem2 = nullptr) { this->subsystem1_ = subsystem1 ?: new Subsystem1; this->subsystem2_ = subsystem2 ?: new Subsystem2; } ~Facade() { delete subsystem1_; delete subsystem2_; } /** * The Facade's methods are convenient shortcuts to the sophisticated * functionality of the subsystems. However, clients get only to a fraction of * a subsystem's capabilities. */ std::string Operation() { std::string result = "Facade initializes subsystems:\n"; result += this->subsystem1_->Operation1(); result += this->subsystem2_->Operation1(); result += "Facade orders subsystems to perform the action:\n"; result += this->subsystem1_->OperationN(); result += this->subsystem2_->OperationZ(); return result; } }; /** * The client code works with complex subsystems through a simple interface * provided by the Facade. When a facade manages the lifecycle of the subsystem, * the client might not even know about the existence of the subsystem. This * approach lets you keep the complexity under control. */ void ClientCode(Facade *facade) { // ... std::cout << facade->Operation(); // ... } /** * The client code may have some of the subsystem's objects already created. In * this case, it might be worthwhile to initialize the Facade with these objects * instead of letting the Facade create new instances. */ int main() { Subsystem1 *subsystem1 = new Subsystem1; Subsystem2 *subsystem2 = new Subsystem2; Facade *facade = new Facade(subsystem1, subsystem2); ClientCode(facade); delete facade; return 0; } 

Output.txt: 実行結果

Facade initializes subsystems: Subsystem1: Ready! Subsystem2: Get ready! Facade orders subsystems to perform the action: Subsystem1: Go! Subsystem2: Fire! 

他言語での Facade

Facade を C# で Facade を Go で Facade を Java で Facade を PHP で Facade を Python で Facade を Ruby で Facade を Rust で Facade を Swift で Facade を TypeScript で