A "cloud database" can take one of two different forms: a traditional database or a NoSQL database installed and running on a cloud virtual machine (public, private or hybrid cloud platform), or a fully managed cloud database as a Service (DBaaS) from a cloud provider ) products and services. The former run their own self-managing database in a cloud environment, which is really no different from operating a traditional database. Cloud DBaaS, on the other hand, is the natural equivalent of a software-as-a-service (SaaS) database: pay as you go, pay only for what you use, and all the details of configuration and scaling are handled by the system to meet demand while maintaining consistent high performance.
Ease of Access and Agility
Scalability and performance
Reliability and Disaster Recovery
Whether your team is developing software on cloud infrastructure or migrating legacy applications to the cloud, cloud-native database products are becoming increasingly popular.
Modern database-as-a-service platforms simplify access to critical resources by providing easy (but controlled) access from cloud and non-cloud systems through consistent APIs and drivers. Centralized and easily accessible databases are especially useful in resource microservice architectures where many applications need to access and share data.
While cloud SQL databases can be used in a variety of situations, the flexibility of today's cloud NoSQL databases greatly increases agility in data management and software development. System upgrades, rebalancing clusters, or provisioning faster hardware can be performed without downtime or even architectural and structural changes.
If you think NoSQL means you have no control over data quality, then perhaps you need to understand how MongoDB provides structural guarantees without sacrificing the ultimate flexibility of the document model.
While some cloud databases are available on all cloud providers (MongoDB Atlas runs on any major public cloud provider), others are specific to a provider (such as Cloud Bigtable on Google or Amazon Web Services on Services RDS).
If you decide on a cloud provider based on your existing footprint, compatibility requirements, or existing relationships, your choice will be a self-managed database on a cloud virtual machine, hosted on or provided by that cloud provider's database-as-a-service offering provided by the supplier.
Other strategies, such as multi-cloud or hybrid cloud, may indicate that you leverage multiple public and private clouds, which narrows your database choices to offerings across providers and/or on-premises.
The platform is locked.
Skill requirements.
Cloud provider policies.
Sign in to leave a comment.