Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

Modern applications require diverse storage architectures to handle different data types, access patterns, and performance requirements. Selecting the wrong storage solution can lead to performance bottlenecks, unnecessary costs, and limits that make it hard to grow.

Akamai’s portfolio includes multiple storage technologies, each optimized for specific use cases. This analysis covers block storage, object storage, managed databases, Akamai NetStorage, and EdgeKV to help you make informed architectural decisions.

Block Storage

Block storage partitions data into fixed-size blocks stored on attached volumes. To be used, these volumes must be mounted to compute instances as virtual disks. They provide low-level storage that operating systems can format with any file system.

Block storage delivers consistent, fast response times and high input/output performance, making it suitable for structured workloads requiring frequent read/write operations. The direct-attached nature ensures consistent performance because volumes connect to instances over the data center’s high-speed internal network rather than the public internet. This reduces latency and provides predictable I/O operations.

Akamai’s Block Storage service attaches directly to Akamai compute instances, providing persistent storage that survives instance lifecycle changes. Volumes can be resized, detached, and reattached as needed.

Primary Use Cases for Block Storage

  • Persistent storage for virtual machines

  • Operating system boot volumes

    Note
    Not all providers use block storage for boot volumes. For example, Akamai compute instances use bundled storage for boot, with block storage used for additional capacity.

Block Storage Cost Structure

Akamai Block Storage pricing is based on allocated storage space per month, regardless of actual usage or access frequency. This predictable pricing model simplifies capacity planning.

Object Storage

Object storage treats data as discrete objects, each containing the data payload, metadata, and a unique identifier. This S3-style storage architecture uses a flat namespace that differs fundamentally from traditional hierarchical file systems. Objects are accessible via HTTP-based APIs and S3-compatible tools, such as s3cmd.

This architecture works well with unstructured data–including images, videos, backups, and log files. Object storage systems scale up easily, and they can offer additional durability if users choose to replicate their data across multiple servers and geographic regions.

Akamai Object Storage provides S3-compatible APIs, and users can store data copies in multiple locations for backup and speed. The service integrates seamlessly with existing S3-compatible tools and workflows. For Akamai Object Storage, the Linode CLI can also be used to access objects.

Primary Use Cases for Object Storage

  • Static website assets (CSS, JavaScript, images)
  • Media storage and content delivery
  • Data archival and disaster recovery
  • Application backups and logs

Object Storage Cost Structure

Pricing for object storage is typically charged per GB stored, plus data transfer fees. This model offers cost efficiency for large-scale storage requirements, backed by high durability guarantees.

Managed Databases

Databases differ from general storage by providing a managed query layer and enforcing relationships among structured data. They optimize for relational or document-based operations rather than simple file storage.

Database software handles indexing, consistency guarantees, and transaction processing. They provide query languages (SQL, NoSQL APIs) and manage complex operations like joins, aggregations, and concurrent access control.

Managed database services provision databases in the cloud so that users don’t have to install and maintain the software on compute instances. Akamai offers managed PostgreSQL and MySQL databases with automated backups, scaling, and maintenance. These services handle database maintenance for you while providing high availability.

Primary Use Cases for Managed Databases

  • Web and mobile application backends
  • Real-time analytics and reporting
  • Business data modeling and relationships
  • Applications requiring ACID compliance for reliable transactions

Managed Database Cost Structure

Managed databases include compute resources, storage, maintenance, and monitoring in their pricing. Higher costs reflect the additional services: automated backups, scaling capabilities, and guaranteed availability.

Akamai NetStorage

NetStorage is Akamai’s established object storage solution that predates the S3 era. It stores files as objects and delivers them via HTTP, similar to modern object storage systems. The service integrates tightly with Akamai’s CDN infrastructure, which is optimized for media files and content distribution. NetStorage serves as origin storage for CDN-delivered content.

A key feature of NetStorage is automatic content replication across geographical regions. This keeps the stored content available at all times, even if one area is hit by a power outage or some sort of network congestion.

Primary Use Cases for Akamai NetStorage

  • Media content origin storage for CDN delivery
  • Software distribution and updates
  • Large file hosting for global audiences

Akamai NetStorage Cost Structure

NetStorage pricing is calculated based on the amount of data stored (either by GB stored or by average GB stored).

Akamai EdgeKV

EdgeKV provides a distributed key-value store for edge computing applications. Unlike traditional storage solutions, EdgeKV stores small pieces of data close to users, powering edge-native architectures for the fastest possible access. EdgeKV is sold separately from EdgeWorkers, but it requires EdgeWorkers to function.

This service handles configuration data, user preferences, authentication tokens, and other small pieces of information that applications need quickly. EdgeKV is not suitable for large or persistent data storage.

Primary Use Cases for Akamai EdgeKV

  • Configuration data and application settings
  • User preferences and personalization data
  • Authentication tokens and session data
  • Feature flags and A/B testing variables
  • Small cache values for edge applications

Akamai EdgeKV Cost Structure

Pricing for EdgeKV is based on the number of operations (reads, writes, deletes, lists) performed, as well as the size of objects (measured in GB) held in durable storage.

Choosing the Right Solution

When selecting storage for your applications, it is essential to evaluate several key factors. The right choice depends on what your enterprise requires across this mix of factors. The table below provides a concise overview of those factors:

Storage TypeData StructurePerformance ProfileDurabilityScalability
Object StorageObjects with metadataHigh throughput, eventual consistencyHigh (replicated)Very high
Block StorageFixed-size blocksConsistent and predictable for moderate I/O needsHigh (persistent)Scales with instance
Managed DatabasesStructured (tables, docs)High consistency, indexed queriesHigh (redundant + backups)Scales vertically and horizontally
Akamai NetStorageObject-likeOptimized for media workflows and software downloadsHighHigh
EdgeKVKey-value pairsUltra-low latency at the edgeMediumEdge-scaled

Data Type and Structure

Consider this table to map your applications’ data types to storage solutions:

RequirementRecommended Solution
Structured data with relationshipsManaged Databases
Unstructured files (images, videos, backups)Object Storage
File system access for applicationsBlock Storage
Small configuration valuesEdgeKV

Access Patterns

Consider this table to map your applications’ access patterns (frequency of access, type of operations) to storage solutions:

RequirementRecommended Solution
Frequent updates and writesBlock Storage, Managed Databases
Infrequent reads with high durabilityObject Storage
Fast access to small data worldwideEdgeKV
Software/media delivery and CDN integrationNetStorage

Performance Requirements

Consider this table to map your applications’ speed and consistency requirements to storage solutions:

RequirementRecommended Solution
Fastest response times for databasesBlock Storage
High throughput for large filesObject Storage
Ultra-fast edge accessEdgeKV
Optimized media deliveryNetStorage

Integration and Compatibility

Consider this table to map existing tools and infrastructure you may already be using to storage solutions:

RequirementRecommended Solution
Direct attachment to serversBlock Storage
S3-compatible tools and APIsObject Storage
Database drivers and connection poolingManaged Databases
CDN and content delivery workflowsNetStorage

Budget Considerations

Consider this table to map your cost structures and budget priorities to storage solutions:

RequirementRecommended Solution
Lowest cost at scaleObject Storage
Predictable monthly costsBlock Storage
Full-service management includedManaged Databases
Integrated CDN pricingNetStorage

Conclusion

Each storage solution addresses specific architectural requirements. Object storage excels for unstructured data at scale, while block storage provides high-performance attached storage. Managed databases handle complex data relationships, and NetStorage integrates with CDN workflows.

Evaluate your data characteristics, access patterns, performance requirements, and budget constraints before making storage decisions. The optimal choice aligns with your application architecture, scalability objectives, and operational requirements.

For applications that require modern object storage capabilities, Akamai Object Storage offers S3-compatible APIs with geographic distribution and competitive pricing.

This page was originally published on


Your Feedback Is Important

Let us know if this guide was helpful to you.


Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.