just-what-we-need-another-aas-discussing-dbaas-and-its-contribution-to-it

Perhaps it is a response to uncertain economic times, or maybe it’s just an inevitable acceptance of all things cloud, but for whatever reasons, the ‘aaS’ model of IT has caught on big time. The ‘aaS’, as it does with ‘SaaS’, ‘PaaS’, ‘IaaS’, etc. means ‘as a Service’. This model of providing IT products requires little upfront investment, making it ideal for startups that need to keep costs light and assets lean, as well as temporary IT needs like trials and testing that don’t call for long-term investments in IT infrastructure.

What is DBaaS?

DBaaS - Database as a Service

One affordable database on the first floor, poolside, please.

DBaaS means database as a service. Companies, developers, and others in need of short or long-term storage can elect to do so in the cloud as a service. Instead of an ouch-inducing cost to buy the hardware needed to set up a database, along with the ho-hum tedium and monotony of getting that DB set up, you can simply lease it aaS. For small companies, startups, and developers in need of temporary database environments, this solution is ideal.

What are the Advantages of DBaaS to the Vendor/Service Provider?

Traditionally, products are sold and people don’t return to spend with the seller again until the end of the product lifecycle, or until they need an additional product. The aaS model flips that around — customers don’t buy anything. The initial cost is lower, but they need the service every day, week, month, and year until they no longer need it. In other words, aaS brings a steady revenue stream in for products that used to be a one-and-done profit. Since the service doesn’t come with a big upfront cost, vendors can ‘sell’ more databases. With virtualization, it’s also really cheap to provide DBaaS, so the profits can be pretty sweet.

What are the Advantages of DBaaS to the Customer?

Vendors aren’t the only ones making out well with DBaaS. Customers can get large and hearty databases up and running quickly, easily, and on the cheap. Databases that would require thousands of dollars in hardware investments can be set up and running for a tiny fraction of that cost in far less time. Plus, DBaaS is a lot more flexible, easy to scale, and simple to manage compared to an onsite database. The customer also transfers most of the responsibility for security onto the DBaaS vendor, which in this age is a tremendous relief. The burden of securing customer and secret proprietary data can consume an enormous portion of the IT budget if it’s done right.

How is VMware a Solution for DBaaS?

DBaaS for Developer

There are several options for using VMware to set up your own DBaaS environment.

VMware developers have lots of options when it comes to setting up their own DBaaS. VMware vFabric Data Director gives developers an easy self-service portal you can use to provision a DB without involving IT. It’s easy to change later, has some great security features, and provides solid backup, restoration, save, development, and testing applications. Alternately, VMware developers can opt for the VMware plus Tintri DBaaS solution or VMware plus Pure Storage solution.

These DBaaS solutions are perfect for setting up your own virtual database or to provide DBaaS products to customers of your own. Looking for a better way to keep up with all things VMware? Sign up for our newsletter today. 

Learn about VMware performance monitoring solutions, new products, partnerships, and more.

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.