containers-and-docker-and-vmware-oh-my-are-docker-containers-the-yellow-brick-road-to-oz

Containers aren’t new. In fact, that technology has been around for years in the form of Linux containers, which Google and other big-name tech companies got on board with and pushed heartily. But containers were a quiet, in the background kind of thing until Docker hit the scene a few years ago. Now the big buzz is whether or not containers will replace virtualization or whether virtualization will squeeze out containers. As it happens, there is room for both. In fact, there is a need for both, and the two can actually support each other.

Are Docker and VMware compatible?

Docker and VMware - compatible?

I guess the better question is, are Container and virtual machines compatible. Both technologies are evolving rapidly. It’s impossible to tell which one will surpass the other, or if there will remain a big place for both.

According to Kit Colbert, VMware’s vice president and CTO of Cloud-Native Apps, "Docker has made significant inroads on reducing complexity and offered greater simplicity and agility for developers. A lot of people in the industry are excited by that, and we’re all trying to figure out how to take what’s happening here and make sure it really works in practice for customers." At a recent VMworld, VMware announced a partnership with Docker, Google, and Pivotal.

Docker isn’t actually a container technology alone, at least not for now. Right now, Docker is really just a container packaging technology that developers can leverage much like VMware vSphere. That means that Docker isn’t a threat for now, but if it develops into a consolidation product (which it will), it will become a direct competitor to virtual machines.

However, Docker isn’t in the clear completely. VM can tout the VMware monitoring capabilities, its maturity, and superior security. Docker is no stranger to criticism about its security, or rather, its lack of. In fact, Docker doesn’t even market itself as a stand alone solution, preferring the adage, "better together".

Where VM’s Efforts are Concentrated

Happy customers need both right now.

Containers aren’t yet well understood in the general marketplace. That could be why so many people are sticking with hypervisor technology until Docker and others prove their worth, stability, and ability to provide enterprise-grade security. Until then, VM is just focusing on happy customers.

VM is simply working towards offering its customers the best possible experience, both with hypervisor and with container technology. According to Colbert, "What we’re focused on is providing the best infrastructure. Compute virtualization, network virtualization, storage technology … What Docker represents is the best way of managing those applications, the provisioning of them. The reality is you still need an infrastructure to provision those applications on. Software doesn’t run on software." Inevitably, containers plus the hypervisor will lead to a greater level of automation.

Of course, both containers and hypervisors are evolving technologies. While VM boasts a strong following, a mature structure, and a more stable, secure environment for applications, containers are young and it’s difficult to say what the future might hold.

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.