Infrastructure Reqs
Complete enterprise infrastructure requirements for self-hosted SettleMint deployment including compute, storage, network, and compliance considerations
Enterprise infrastructure planning overview
Planning enterprise blockchain infrastructure requires careful consideration of performance, security, compliance, and total cost of ownership. This guide provides detailed requirements for production-grade SettleMint deployments.
Enterprise Resource Planning
The requirements listed below are for the core platform components only. Additional resources will be needed for:
- Prerequisites (databases, monitoring, security services)
- Blockchain services you plan to deploy
- High availability and disaster recovery systems
- Development, staging, and production environments
How much compute power do I need for enterprise blockchain deployment?
Development/Testing Requirements
- CPU: 4 cores (Intel/AMD x86-64)
- RAM: 16GB DDR4
- Storage: 100GB SSD
- Network: 1 Gbps
Use Cases:
- Developer testing
- Proof of concept
- Integration testing
- Training environments
Cost Estimate: $200-500/month for cloud instances
Minimum requirements are suitable for testing and development environments only. Not suitable for production workloads or compliance requirements.
Enterprise Production Requirements
- CPU: 8+ cores (Intel Xeon or AMD EPYC recommended)
- RAM: 32GB DDR4 ECC
- Storage: 500GB+ NVMe SSD
- Network: 10 Gbps with redundancy
Use Cases:
- Single-region production deployment
- Small to medium enterprise workloads
- Up to 1000 transactions per minute
- Standard compliance requirements
Cost Estimate: $800-1500/month for cloud instances
These specifications provide adequate performance for most enterprise production workloads with room for growth.
High-Availability Enterprise Requirements
- CPU: 16+ cores per node (3+ nodes)
- RAM: 64GB+ DDR4 ECC per node
- Storage: 1TB+ NVMe SSD per node
- Network: 25 Gbps with full redundancy
Use Cases:
- Multi-region deployment
- Large enterprise workloads
- 10,000+ transactions per minute
- Strict compliance and audit requirements
- 99.99% uptime requirements
Cost Estimate: $3000-8000/month for cloud instances
High-availability setups require 3x minimum resources across multiple availability zones or regions for true enterprise resilience.
What network infrastructure do I need for enterprise blockchain security?
Enterprise blockchain deployments require robust network security, compliance capabilities, and high availability. The platform requires specific network configurations to ensure secure and reliable communication between components:
Connectivity
- Internet Access: Required for pulling container images and updates
- Load Balancer: For distributing traffic across nodes
- Ingress Controller: For routing external traffic
- SSL/TLS: Valid certificates for secure communication
Required Ports
- 80/443: HTTP/HTTPS traffic
- 6443: Kubernetes API server
- 30000-32767: NodePort services range
- 10250: Kubelet API
- 179: Calico BGP (if using Calico)
Network Security We recommend implementing network policies and security groups to control traffic flow between components.
Storage requirements
Proper storage configuration is crucial for platform stability and performance. Consider the following requirements:
Performance Requirements
- Type: SSD storage required for all components
- IOPS: Minimum 3000 IOPS for database volumes
- Latency: < 10ms average latency
- Throughput: 125MB/s minimum for database volumes
Capacity Planning
- Initial Allocation: Start with recommended sizes
- Growth Buffer: Plan for 30% annual growth
- Backup Storage: Equal to primary storage
- Monitoring: Implement storage usage alerts
Storage best practices
- Use separate volumes for different components
- Implement regular backup procedures
- Monitor storage performance metrics
- Set up alerts for capacity thresholds
Prerequisites resource requirements
When hosting prerequisites on the same infrastructure, these requirements must be added to the base platform specifications. Each component can be hosted separately or together depending on your architecture.
PostgreSQL
Resource Requirements
- CPU: 2 cores
- RAM: 4GB
- Storage: 50GB SSD
Recommendations
- High IOPS SSD storage
- Regular backups
- Consider high availability setup
Redis
Resource Requirements
- CPU: 2 cores
- RAM: 4GB
- Storage: 20GB SSD
Recommendations
- In-memory performance
- Persistence configuration
- Consider clustering for HA
MinIO
Resource Requirements
- CPU: 2 cores
- RAM: 8GB
- Storage: 100GB+ SSD
Recommendations
- Scalable storage setup
- Regular capacity monitoring
- Backup strategy required
HashiCorp Vault
Resource Requirements
- CPU: 2 cores
- RAM: 4GB
- Storage: 20GB SSD
Recommendations
- High availability setup
- Auto-unsealing configuration
- Regular key rotation
Production considerations
These are baseline requirements. For production environments, consider:
- High availability configurations may require 2-3x these resources
- Monitoring and logging overhead
- Backup storage requirements
- Scaling headroom for growth
Total resource summary
For a production setup hosting both platform and prerequisites:
CPU
- Platform: 8 cores
- Prerequisites: 8 cores
- Total: 16+ cores
RAM
- Platform: 32GB
- Prerequisites: 20GB
- Total: 52GB+
Storage
- Platform: 250GB
- Prerequisites: 190GB
- Total: 440GB+
Service requirements
The platform allows you to deploy services in two ways:
- On the same cluster as the platform
- On separate target clusters
Same Cluster Deployment
If you plan to deploy services on the same cluster as the platform:
- Add service requirements to the platform requirements
- Include them in capacity planning
- Account for resource overhead
- Plan for scaling headroom
Target Cluster Deployment
Using separate target clusters for services:
- Keeps platform and service workloads isolated
- Requires separate infrastructure planning
- Can be optimized for specific service needs
- Enables geographic distribution
Infrastructure planning strategy
We recommend:
- List all services you plan to deploy
- Decide on deployment strategy (same cluster or target clusters)
- For same cluster: Add service requirements to platform requirements
- For target clusters: Plan separate infrastructure
- Include 30% buffer for growth and peak loads
Example calculation
Let's calculate requirements for a setup with:
- 2 Polygon nodes (Mainnet & Mumbai)
- 1 Hyperledger Besu node
- 1 Smart Contract Portal
- 1 Integration Studio
- 1 Blocksout Explorer
Service Requirements (Medium size, Dedicated mode):
-
Polygon Nodes (2x):
- CPU: 2 × 1.5 cores = 3 cores
- RAM: 2 × 1.0 GB = 2 GB
- Storage: Minimal
-
Besu Node (1x):
- CPU: 1.5 cores
- RAM: 2.5 GB
- Storage: 100 GB
-
Smart Contract Portal:
- CPU: 2.0 cores
- RAM: 2.0 GB
- Storage: 10 GB
-
Integration Studio:
- CPU: 2.0 cores
- RAM: 4.0 GB
- Storage: 10 GB
-
Blocksout Explorer:
- CPU: 2.0 cores
- RAM: 4.0 GB
- Storage: 50 GB
Same Cluster Approach:
- Total CPU: 27+ cores (16 platform/prereqs + 11 services)
- Total RAM: 67GB+ (52GB platform/prereqs + 15GB services)
- Total Storage: 620GB+ (440GB platform/prereqs + 180GB services)
Target Cluster Approach:
- Platform Cluster: 16+ cores, 52GB+ RAM, 440GB+ storage
- Service Cluster: 11+ cores, 15GB+ RAM, 180GB+ storage
On-Premise Deployment
Complete guide to self-hosted SettleMint deployment for enterprises requiring data sovereignty, compliance, and air-gapped infrastructure
Platform Install
Step-by-step enterprise deployment guide for SettleMint Platform using Helm with production-ready configurations, security hardening, and multi-cluster support