Network topology diagram

From Server rental store
Revision as of 17:28, 15 April 2025 by Admin (talk | contribs) (Automated server configuration article)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Network Topology Diagram

This article details the network topology of our MediaWiki server infrastructure, providing a visual and technical understanding for new administrators and developers. Understanding this topology is crucial for troubleshooting, maintenance, and scaling the wiki. This documentation focuses on the physical and logical arrangement of servers, network devices, and connections.

Overview

Our MediaWiki installation utilizes a three-tier architecture: web servers, application servers, and database servers. This separation allows for scalability, improved security, and easier maintenance. The network is designed for high availability and redundancy. A dedicated Load Balancer distributes traffic across the web servers. All servers are behind a Firewall for security. We utilize Virtualization technology for several components. Detailed information regarding Security Policy is available elsewhere.

Physical Topology

The physical topology outlines the physical location and connections of our servers and network devices. All servers are housed in a dedicated data center with redundant power and cooling.

Component IP Address (Example) Role Location (Rack/Unit)
Load Balancer 192.168.1.10 Traffic Distribution Rack A / 1
Web Server 1 192.168.1.20 Serving Wiki Pages Rack A / 2
Web Server 2 192.168.1.21 Serving Wiki Pages Rack A / 3
Application Server 1 192.168.1.30 Processing Wiki Logic Rack B / 1
Application Server 2 192.168.1.31 Processing Wiki Logic Rack B / 2
Database Server 1 192.168.1.40 Storing Wiki Data Rack B / 3
Database Server 2 192.168.1.41 Storing Wiki Data (Replica) Rack B / 4
Firewall 192.168.1.1 Network Security Rack C / 1

Logical Topology

The logical topology describes how the servers communicate with each other. We utilize a private network for internal communication between the servers, separate from the public network accessible via the Load Balancer. The DNS Configuration is critical for resolving server names. The application servers access the database servers via a dedicated network interface.

Connection Protocol Source Destination Purpose
Web Server <-> Load Balancer HTTP/HTTPS Web Server Load Balancer Wiki Page Requests
Load Balancer <-> Web Server HTTP/HTTPS Load Balancer Web Server Distributing Traffic
Application Server <-> Web Server HTTP Application Server Web Server Rendering Dynamic Content
Application Server <-> Database Server MySQL Application Server Database Server Accessing Wiki Data
Database Server 1 <-> Database Server 2 Replication Protocol Database Server 1 Database Server 2 Database Replication

Server Specifications

The following table details the hardware specifications for each server type. These specifications are subject to change as we upgrade our infrastructure. See the Capacity Planning document for details on future upgrades. The Monitoring System provides real-time performance data.

Server Type CPU Memory (RAM) Storage Operating System
Web Server Intel Xeon E5-2680 v4 32 GB 1 TB SSD Ubuntu Server 20.04 LTS
Application Server Intel Xeon E5-2690 v4 64 GB 500 GB SSD Ubuntu Server 20.04 LTS
Database Server Intel Xeon E5-2697 v4 128 GB 2 TB RAID 10 CentOS 7

Network Devices

The network relies on several key devices for connectivity and security. These devices are regularly maintained according to our Maintenance Schedule.

  • Router: Connects our network to the internet.
  • Switch: Provides connectivity between servers within the data center.
  • Firewall: Protects our network from unauthorized access.
  • Load Balancer: Distributes traffic across web servers.

Future Considerations

We are currently evaluating a move to a containerized environment using Docker and Kubernetes to further improve scalability and resource utilization. We are also investigating the use of a Content Delivery Network (CDN) to improve performance for users in different geographical locations.



Main Page Help:Contents MediaWiki FAQ Configuration Settings Database Schema Extension Installation Server Administration Troubleshooting Guide Security Best Practices Performance Tuning Backup and Recovery Load Balancing Firewall Configuration DNS Management Virtualization Platform Monitoring Tools


Intel-Based Server Configurations

Configuration Specifications Benchmark
Core i7-6700K/7700 Server 64 GB DDR4, NVMe SSD 2 x 512 GB CPU Benchmark: 8046
Core i7-8700 Server 64 GB DDR4, NVMe SSD 2x1 TB CPU Benchmark: 13124
Core i9-9900K Server 128 GB DDR4, NVMe SSD 2 x 1 TB CPU Benchmark: 49969
Core i9-13900 Server (64GB) 64 GB RAM, 2x2 TB NVMe SSD
Core i9-13900 Server (128GB) 128 GB RAM, 2x2 TB NVMe SSD
Core i5-13500 Server (64GB) 64 GB RAM, 2x500 GB NVMe SSD
Core i5-13500 Server (128GB) 128 GB RAM, 2x500 GB NVMe SSD
Core i5-13500 Workstation 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000

AMD-Based Server Configurations

Configuration Specifications Benchmark
Ryzen 5 3600 Server 64 GB RAM, 2x480 GB NVMe CPU Benchmark: 17849
Ryzen 7 7700 Server 64 GB DDR5 RAM, 2x1 TB NVMe CPU Benchmark: 35224
Ryzen 9 5950X Server 128 GB RAM, 2x4 TB NVMe CPU Benchmark: 46045
Ryzen 9 7950X Server 128 GB DDR5 ECC, 2x2 TB NVMe CPU Benchmark: 63561
EPYC 7502P Server (128GB/1TB) 128 GB RAM, 1 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (128GB/2TB) 128 GB RAM, 2 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (128GB/4TB) 128 GB RAM, 2x2 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (256GB/1TB) 256 GB RAM, 1 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (256GB/4TB) 256 GB RAM, 2x2 TB NVMe CPU Benchmark: 48021
EPYC 9454P Server 256 GB RAM, 2x2 TB NVMe

Order Your Dedicated Server

Configure and order your ideal server configuration

Need Assistance?

⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️

Retrieved from "https://serverrental.store/index.php?title=Network_topology_diagram&oldid=1988"