the-new-vmware-motto-one-cloud-any-app-any-device

If you do much reading in the world of VMware, you’ll soon encounter the phrase, ‘One Cloud, Any App, Any Device." What does this term mean? Is this just a cool marketing slogan tossed out there by VMware, or is there some actual meaning and substance behind it?

The Environment Enabling ‘One Cloud’

One Cloud, Any App, Any Device

Management of the cloud environment will be made so easy that apps and data can be moved about within different clouds, both on and off premises, seamlessly and effortlessly. It will essentially act as one cloud.

In order to understand the term, you have to remember the full landscape of today’s tech environment. While the concepts of mobile, cloud, data, analytics, and security used to be separate, these ideas have now converged into more or less a single entity with multiple parts. While not all of the cloud is dedicated to mobile, mobile apps are inherently dependent on the cloud. While not all data resides in the cloud, an enormous part of the cloud is dedicated to data and data analytics. In fact, data is one of the biggest drivers for demand of cloud storage and processing capabilities. Security isn’t limited to mobile apps or the cloud or even big data, per se, but try to engage in any one of those without the right security, and it’s a recipe for disaster.

So, this is the situation. These technologies are not one, but they are working together, driving each other, and married to an extent that they are not likely to be parted anytime in our lifetimes. At the same time, open source is absolutely taking over the computing world. Open source is driving big data analytics (Hadoop), it’s behind much of the mobile movement (mobile devices are largely powered by Linux operating systems, particularly Ubuntu), and is a significant player in the field of cloud computing, too (OpenStack, Docker, and MongoDB, just to name a few).

What ‘One Cloud’ is and What It Isn’t

One Cloud

The line between the virtual world and the physical world continue to blur.

VMware’s vision is to conglomerate the cloud into essentially one. One cloud powering all of the devices (mobile and desktop) and all of the apps on those devices. Sound far fetched? It’s already beginning to happen with Windows 10, where IT departments are able to manage complete suites of Windows 10 apps collectively.

This doesn’t mean doing away with all of the individual cloud environments in favor of a single cloud environment, but rather making management of the cloud so easy  that data and applications and other services move about within the collective cloud environment so seamlessly and effortlessly that it essentially behaves as one cloud. This vision keeps the consumer end simple and intuitive, while boosting the back end with the enterprise-grade security it takes to assure data protection in today’s environment.

VMware has recently backed up their concepts by partnering with a couple of giants that would seem to be more competitors than allies — Microsoft and Google. But the spirit of coopetition is intense as the cloud and other technologies shake out to become what they will inevitably become. The lines between the virtual and the physical are blurring already.

Ready to begin simplifying your virtualized environment to take advantage of the ‘One Cloud’ easy management concept? 

Visit Opvizor.com to learn more and register for the VMware Health analyzer today.

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.