vsan-hybrid-vs-all-flash

vSAN: Hybrid vs. All Flash

We would like to continue our vSAN series with Mayur Parmar’s very helpful blog posts. Please find the complete article from Mayur here and scroll down for some more information.

VMware vSAN is a software defined storage solution from VMware to eliminate the need of the additional storage boxes using the local server storage. In simple words – vSAN abstracts the local storage of ESXi hosts and makes a pool of it to be used as a shared storage which is very much optimized. So as you are using the local storage you will not need additional storage boxes for the storing files which also helps in lowering the Total Cost of Ownership (TCO).

vSan uses the local server’s disk to create a data store. Disk in the server can be of multiple types such as SAS, NL-SAS, SATA, SSD, NVMe etc.

In vSAN you can use 2 different configurations based on your requirements which is Hybrid or All Flash. vSAN uses the Cache Tier and the Capacity Tier. Cache Tier is used for read cache performance while Capacity Tier makes the capacity for storing the data.

vSAN

Photo courtesy of tsmith.co

vSAN Hybrid

As the name suggests it is a Hybrid configuration of disks. vSAN Hybrid consists of 1 SSD for caching and 1 or more HDDs for the Capacity. SSD will be used for the caching which consists of the Read Cache and Write buffer. So 70% of the SSD Drive will be used as a Read Cache for reading the data which will increase the performance while accessing the data and 30% of the SSD Drive will be userd as a Whrite Cache.

This is a quick abstract from Mayur’s article, please find here more.

vSAN All Flash

As the name suggests it is an All Flash configuration of disks where all the SSDs will be used for the Cache and the Capacity Tier. There will be NO HDDs in this configuration. vSAN All Flash consists of the 1 SSD for the Cache Tier and 1 or more SSDs for the Capacity Tier. There is no Read Cache available in All Flash configuration as data is directely read from the Capacity Tier which are already SSD so you will get the performance boost.

Cache Disk in All Flash will act as an write buffer only so data is written directly to the Cache Tier and then it will be destraged onto the Capacity Tier. Capacity Tier will consist of all the SSDs available in the ESXi hosts.

This is a quick abstract from Mayur’s article, please find here more.

Download Performance Analyzer

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.