In Uzbekistan's modern IT infrastructure, which is undergoing intensive digital transformation under the national strategy 'Digital Uzbekistan 2030,' the choice of data storage architecture has moved beyond being a purely technical question into the realm of strategic business planning. For CIOs and system architects, understanding the fundamental differences between object storage (S3) and block storage is a critical factor in ensuring fault tolerance, scalability, and regulatory compliance.
Cloud services provided by national operators such as UzCloud are built on cutting-edge hardware solutions, enabling complex architectural scenarios with a total storage capacity reaching 10 petabytes.
Chapter 1. Theoretical Foundations and Historical Context
The evolution of data storage methods has progressed from early file system implementations to modern distributed cloud platforms. A fundamental shift occurred in 1988 with the introduction of POSIX standards, which defined hierarchical file structures and access methods. However, the advent of Amazon S3 in 2006 marked the beginning of a revolution, offering an alternative to rigid hierarchical trees in the form of a flat namespace.
Block storage is inherently the closest to the physical hardware level. It divides data into equally-sized fixed blocks, each with a unique address but lacking extended metadata. Object storage (S3) operates on objects — complete data units that include the content itself, a unique identifier (key), and a rich set of metadata.
Comparative Characteristics of Base Models
| Characteristic | Block Storage | Object Storage (S3) |
|---|---|---|
| Data unit | Fixed-size block | Object (Data + Metadata) |
| Access interface | Low-level protocols (iSCSI, FC) | RESTful API (HTTP/HTTPS) |
| Structure | Hierarchical (via file system) | Flat (buckets and keys) |
| Metadata | Minimal (block address) | Extended, customizable |
| Data modification | Updating individual blocks | Full object rewrite |
Chapter 2. Block Storage Architecture: Low-Level Control
Block storage in the UzCloud cloud environment is presented to the user as a raw disk that can be mounted to a virtual machine. Once mounted, the server's operating system manages it just like a local hard drive, creating partitions and formatting them into the chosen file system — EXT4, XFS, or NTFS.
The main advantage of the block approach is predictable performance and extremely low latency. Since data exchange occurs at the block level through a specialized storage area network (SAN), overhead is minimal. This is critical for latency-sensitive applications such as transactional databases (OLTP).
Despite their high speed, block storage systems have inherent limitations when it comes to horizontal scaling. Expanding a volume often requires manual administrator intervention. The traditional one-to-one relationship between a host and a volume makes it difficult for multiple servers to share data simultaneously.
Chapter 3. S3 Object Storage: A New Paradigm
UzCloud's S3 object storage offers a radically different approach, designed for storing massive volumes of unstructured data. Data is stored in logical containers — buckets — whose capacity is virtually unlimited. Each object is identified by a unique key and is accessible via standard HTTP calls from anywhere on the internet.
The S3 API standard has become the de facto industry standard, supported by most modern development tools, SDKs, and backup systems. This makes S3 an ideal choice for cloud-native applications that can directly upload and download data using standard libraries for Java, Python, Go, or CLI tools.
Key S3 Features
| S3 Feature | Description and Business Value |
|---|---|
| Versioning | Storing multiple versions of a single object to protect against accidental deletion |
| Object Lock | WORM (Write Once, Read Many) model for compliance requirements |
| Multipart upload | Multipart upload for files >100 MB, improving transfer reliability |
| Geo-replication | Automatic data copying between availability zones |
Chapter 4. Technical Comparison of Performance and Reliability
Object storage introduces additional latency due to the use of the HTTP protocol. Time to first byte (TTFB) in S3 is measured in milliseconds, while in Block Storage it is in the microsecond range. However, during massive parallel data processing, S3 can outperform block systems in aggregate throughput.
Data storage reliability in S3 is achieved through automatic creation of multiple copies of each object and their distribution across geographically remote availability zones. This enables durability rates of 99.99999%. The SLA for both storage types in UzCloud is 99.95%.
Chapter 5. Uzbekistan Market Specifics: TAS-IX and Legislation
Using UzCloud resources located within the national network segment provides a number of critical advantages for TAS-IX users.
- High speed: bandwidth up to 1 Gbps for all subscribers within the country
- Cost savings: traffic within TAS-IX is often unmetered or significantly cheaper than international traffic
- Low ping: minimal latency from Tashkent, Bukhara, or Fergana
Under Article 27¹ of the Law of the Republic of Uzbekistan 'On Personal Data,' all operations involving the processing of citizens' personal data must be carried out on technical facilities physically located within the territory of Uzbekistan. This makes it impossible to use global providers (AWS, Azure) for storing customer databases.
Chapter 6. Economic Analysis and Total Cost of Ownership
In block systems, the client pays for provisioned capacity. If a 1 TB volume is created but only 100 GB of data is stored, the bill will be for the full terabyte. This requires careful capacity planning to avoid unjustified expenses.
S3 Storage Tiers
| S3 Storage Type | Features | Economic Impact |
|---|---|---|
| Standard (Hot) | Actively used data | Highest cost per GB, low cost per request |
| Cold (IceBox) | Infrequent access (backups) | Low cost per GB, high cost per request |
| Glacier (Archive) | Long-term storage | Minimum cost per GB, long retrieval time |
Chapter 7. Business Cases in Uzbekistan
Banking sector: remote banking systems require the highest transaction processing speeds — Block Storage based on SSD/NVMe for PostgreSQL/Oracle. Simultaneously, S3 is used to store digital archives of credit files and passport scans, enabling compliance with data localization requirements.
E-commerce: the main product catalog is stored in a database on Block Storage, while millions of images reside in S3. A bucket is configured as a static website, allowing images to be served directly via TAS-IX, minimizing server load.
Government information systems: combining Block Storage for operational data and S3 (Cold Storage) for archival documents. S3 lifecycle policies allow automatic migration of documents that have not been accessed for more than 6 months to a 'cold' storage tier.
Conclusion
The choice between S3 and Block Storage is not a zero-sum game. In an effectively designed system, both storage types complement each other. If performance and low latency are the priority — Block Storage. If unlimited scalability and unstructured data storage are required — S3. Given Uzbekistan's regulatory requirements, both storage types must be hosted locally — UzCloud's infrastructure ensures the necessary compliance with ZRU-547.