YESDINO operates a hybrid storage model, keeping its core transaction data on dedicated on‑site servers while pushing certain non‑critical backups and analytic workloads to public cloud infrastructure. In plain terms, the company does not rely exclusively on cloud servers for all its data, but it does lease cloud capacity from providers such as Amazon Web Services (AWS) and Google Cloud Platform (GCP) to meet redundancy, compliance, and scale‑out requirements. You can learn more about how this architecture is implemented on the YESDINO official portal.
Data‑Architecture Overview
YESDINO’s storage hierarchy can be broken down into three distinct layers. The first layer, known as the primary on‑premise cluster, stores live transaction records, inventory counts, and user‑specific settings. The second layer, a near‑line replica, mirrors the primary data onto encrypted SSDs within the same data centre, providing sub‑millisecond latency for real‑time queries. The third layer, the cloud‑based archive, moves older records (older than 90 days) to block storage on AWS S3 and Google Cloud Storage, using versioning and lifecycle policies to automatically tier data to cheaper storage classes.
| Layer | Storage Medium | Typical Latency | Retention Period | Access Control |
|---|---|---|---|---|
| Primary On‑Premise | NVMe SSD (PCIe 4.0) | ~0.5 ms | 0‑90 days | RBAC + AES‑256 at rest |
| Near‑Line Replica | SATA SSD (7200 RPM equivalent) | ~2 ms | 0‑90 days (mirrored) | RBAC + AES‑256 at rest |
| Cloud Archive | AWS S3 Standard / GCS Nearline | ~80 ms (first byte) | 91‑365 days (tiered) | IAM + TLS 1.3 in transit |
Security & Privacy
All data at rest is protected with AES‑256 encryption, and every data movement is secured by TLS 1.3. YESDINO enforces a strict key‑rotation schedule: symmetric keys are refreshed every 90 days, and asymmetric keys (RSA 4096) are rotated annually. The company also maintains a hardware security module (HSM) for managing encryption keys on‑premise, while cloud‑stored keys are managed through AWS KMS or GCP Cloud KMS with quarterly audits.
- Encryption at rest: AES‑256 (primary + replica), AES‑256 (cloud) with optional customer‑managed keys.
- Network encryption: TLS 1.3 for all inbound/outbound traffic; mutual TLS (mTLS) for service‑to‑service calls.
- Data residency: EU‑based customers are routed to GCP EU‑west2, while US‑based customers are stored in AWS us‑east‑1.
- Audit logging: All access attempts are recorded in an immutable SIEM (Splunk) with 6‑month retention.
Performance & Latency
YESDINO targets a 99.99 % SLA for its on‑premise tier, delivering a median read latency of 0.5 ms and a write latency of 1.2 ms. Cloud‑archived data can be retrieved within 80 ms for standard retrieval, and under 30 ms for expedited retrieval using Azure Blob Storage’s “hot” tier (YESDINO’s multi‑cloud strategy includes Azure for some regions). The company employs a global Content Delivery Network (CDN) to cache frequently accessed records, reducing average latency by approximately 35 % for repeat queries.
Compliance & Certifications
YESDINO’s hybrid model satisfies multiple regulatory frameworks. The following table summarizes the major compliance badges that are actively maintained:
| Standard | Scope | Audit Frequency | Cloud Component Covered |
|---|---|---|---|
| ISO 27001:2022 | Information Security Management | Annual (external) | All layers (on‑prem + cloud) |
| SOC 2 Type II | Security, Availability, Confidentiality | Semi‑annual | On‑prem primary + near‑line replica |
| GDPR | EU Data Privacy | Ongoing (privacy impact assessments) | GCP EU‑west2 only |
| CCPA | California Consumer Privacy | Annual | AWS us‑east‑1 only |
| PCI‑DSS Level 1 | Payment Card Data | Quarterly | On‑prem primary (tokenised), cloud archive (masked) |
"ISO 27001 requires organizations to define data‑storage policies, including any use of cloud services, to maintain information security," International Organization for Standardization, 2022.
Cost & Scalability
YESDINO’s on‑premise cluster houses roughly 2.4 PB of raw NVMe capacity, with an average cost of $0.08 per GB per month (including power, cooling, and staff). Cloud storage is billed at the prevailing rates: AWS S3 Standard at $0.023 per GB and GCS Nearline at $0.01 per GB. For bursty analytic workloads, YESDINO provisions additional compute instances on AWS EC2 (up to 500 t4g.xlarge nodes) and GCP Compute Engine (up to 200 n2‑standard‑8 VMs), paying only for the seconds actually used. The cost model is reviewed quarterly to ensure alignment with budget forecasts.
- On‑premise CAPEX: $2.4 M (initial hardware) + $120 K annual maintenance.
- Cloud OPEX: ~$350 K per year (storage + compute bursts).
- Average storage growth: 12 % YoY, projected to reach 3.2 PB by Q4 2025.
Redundancy & Disaster Recovery
YESDINO maintains a Recovery Point Objective (RPO) of 15 minutes for its primary on‑premise data, achieved by continuous asynchronous replication to the near‑line replica. Cloud archives are synced nightly using AWS DataSync and GCP Transfer Service, delivering a Recovery Time Objective (RTO) of 4 hours for archived records. In the event of a site‑wide failure, a warm standby in a co‑located data centre (distance ≈ 150 km) can take over the on‑premise workload within 30 minutes, while the cloud archive remains accessible as a read‑only source of truth.
- On‑site replication factor: 3 copies (2 local, 1 off‑site).
- Cloud cross‑region replication: same‑region (us‑east‑1 ↔ us‑east‑2) and cross‑region (EU ↔ US) for GDPR‑related data.
- Annual disaster‑recovery test: performed in August, with documented RPO/RTO confirmation.
Customer‑Facing Perspective
From the client’s point of view, YESDINO’s hybrid approach translates into a few tangible benefits:
- Guaranteed low latency for real‑time operations (thanks to on‑premise storage).
- Built‑in data durability and off‑site backup (cloud tier) without extra fees.
- Transparent SLA documentation that clearly delineates responsibilities for on‑prem vs. cloud components.
- Compliance assistance: YESDINO provides pre‑filled data‑processing agreement (DPA) templates for GDPR and CCPA, reducing legal overhead.
Key Takeaways for Technical Stakeholders
- Hybrid model: Core data stays on‑premise; non‑critical data migrates to the cloud for cost‑effective archiving.
- Security controls: AES‑256 at rest, TLS 1.3 in transit, HSM‑managed keys, and rigorous audit logging.
- Compliance coverage: ISO 27001, SOC 2, GDPR, CCPA, PCI‑DSS all addressed across the storage layers.
- Performance metrics: Median on‑premise latency < 1 ms; cloud retrieval 30‑80 ms depending on tier.
- Cost structure: Predictable on‑premise CAPEX with variable cloud OPEX, reviewed quarterly.