IT and software
On-premise server layout
An on-premise server layout rack by rack, with the redundant power feeds and network links drawn as separate paths
This drawing comes from one YAML file. No shape was moved by hand.
Notes in the source (in Japanese)
構成図の値打ちは、箱ではなく「どこで切れるか」。利用者 → Apache → PHP-FPM → MariaDB と並べると、止まったときにどこまで届くかが読める。
バックアップ先(Wasabi)を同じ箱の中に描くと、本番機ごと失ったときに戻せないことが図から消える。だから保管先は、別の群として離して置く。
昼間は誰も通らない経路でも、DB を触っている。図に出ていない経路は、点検されない。夜間バッチは DB のダンプも Wasabi へ書き出す(バックアップの線を描き落とさない)。
mod_php は PHP を Apache の中で動かす方式、PHP-FPM は別プロセスへ FastCGI で渡す方式。両方を書くと、どちらで動いているかが図から読めない。FPM へ渡すのは mod_proxy_fcgi(Apache 2.4 の公式文書が FPM との組み合わせを説明しているhttps://httpd.apache.org/docs/2.4/mod/mod_proxy_fcgi.html 、2026-09-29 取得)。
Source (YAML)
examples/gallery/01-オンプレのサーバ構成.zumen.yaml
More in this field
A cloud architecture showing the VPC and its subnets, and where the load balancer, application, database and object store sit
Where data goes from collection through transformation, storage and aggregation to display, and what kind of container holds it at each step
A network layout of the links and equipment between sites, with the address range carried by each segment
An order management ER diagram with primary and foreign keys, and the one-to-many relationships drawn as crow feet
A server room where racks face each other to make hot and cold aisles, with the clearance of each aisle written in
A UML class diagram where inheritance, realisation, association and aggregation are told apart by line type and end symbol
A UML state machine with transitions, the events and guards that fire them, and the pseudostates that begin and end it
A UML use case diagram with the actors, the use cases, and the include and extend relationships between them