Nami Cloud offers two ways to interact with decentralized storage. Both services use Walrus as the underlying storage layer, but provide different interfaces and feature sets. This guide helps you choose between S3-Compatible Storage and Walrus Publisher Raw API based on your specific requirements.

​
Service Comparison Overview

FeatureS3-Compatible StorageWalrus Publisher API
LatencySeveral hundreds milliseconds~10s upload + 10s availability
Storage RenewalAutomatic (hands-free)Manual epoch management
API StyleStandard S3 REST APICustom Walrus Protocol
Learning CurveMinimal (familiar S3)Moderate (new concepts)
Existing Tool SupportFull AWS SDK supportCustom integration required
PerformanceFast with Railgun (Beta)Direct network access
Analytics & MonitoringSupport metricsSupport metrics
Storage Epoch ControlAutomated (hands-free)Manual control available
Web3 IntegrationAbstracted layerDirect blockchain access

​
Detailed Service Analysis

​
S3-Compatible Storage

​
When to Choose S3-Compatible

  • Migrating from AWS S3 - Zero code changes required
  • Rapid prototyping - Get started immediately with familiar tools
  • Simple storage needs - Just upload/download files without complexity
  • Team familiarity - Developers already know S3 APIs
  • Third-party integrations - Using tools that expect S3 endpoints

​
Advantages

  • Zero Migration Friction - Works with existing S3 code and tools
  • Automatic Management - Built-in encryption, renewal, and optimization
  • Familiar Interface - Standard S3 operations (PUT, GET, DELETE, LIST)
  • Railgun Acceleration (Beta) - Built-in performance optimization
  • SDK Support - Works with AWS SDK in all major languages
  • Quick Setup - Start storing data in minutes

​
Disadvantages

  • Limited Visibility - Less insight into underlying Walrus operations
  • S3 Limitations - Constrained by S3 API design patterns

​
Walrus Publisher Raw API

​
When to Choose Publisher API

  • Web3 applications - Need direct blockchain verification and control
  • Custom workflows - Building specialized storage integrations

​
Advantages

  • Multi-Endpoint Management - Control multiple publishers across regions
  • Comprehensive Analytics - Detailed metrics, logs, and performance data
  • Direct Walrus Access - Full control over storage epochs and blockchain operations
  • Flexible Configuration - Custom settings for specific use cases

​
Disadvantages

  • Higher Latency - 10s upload + 10s availability
  • Manual Management - Need to manage storage epochs
  • Steeper Learning Curve - Need to understand Walrus protocol concepts
  • Custom Integration - No existing SDK support, must build own client
  • More Complex Setup - Requires configuration of endpoints and monitoring
  • No S3 Tool Support - Cannot use existing S3 CLI tools or libraries
  • Higher Development Cost - More time needed for implementation

​
Performance & Scalability Comparison

​
Latency & Throughput

S3-Compatible Storage

  • Railgun Acceleration (Beta): Sub-100ms globally
  • Single Endpoint: Optimized for simplicity
  • Auto-caching: Built-in edge acceleration
  • Standard Operations: PUT/GET with S3 semantics

Walrus Publisher API

  • Direct Network Access: Native Walrus performance
  • Multi-Endpoint: Load balancing across publishers
  • Geographic Optimization: Route to nearest publisher
  • Batch Operations: Efficient bulk upload/download

​
Code Examples Comparison

import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";

const s3Client = new S3Client({
  endpoint: "https://my-bucket.storage.nami.cloud",
  credentials: {
    accessKeyId: "your-access-key", 
    secretAccessKey: "your-secret-key"
  }
});

// Upload file - standard S3 API
await s3Client.send(new PutObjectCommand({
  Bucket: "my-bucket",
  Key: "file.jpg",
  Body: fileBuffer
}));