APJ - ISV - Database

O'Reilly eBook: An Introduction to Cloud Databases

Issue link: https://resources.awscloud.com/i/1496544

Contents of this Issue

Navigation

Page 24 of 47

Vendors offer numerous options to match your usage to your needs and significantly reduce your spending. For instance, by purchasing reserved instances in AWS, you might be able to dramatically reduce costs. In general, careful planning can let you predict your needs at any particular time and eliminate the overprovisioning that on- premises datacenters need to do. Effects on architecture and application design The architecture of cloud-based databases is inherently quite differ‐ ent from that of a traditional, on-premises database in a datacenter. You must take into account multiple geographic regions and AZs, different types of network designs, and other cloud-specific features when planning your database deployments. The DBA must keep in close contact with application developers to understand their needs and provide the best fit in the cloud at the lowest possible cost. Tracking license compliance Proprietary databases are offered in the cloud through two basic licensing models: license included or bring your own license (BYOL). The latter model is valuable if you already have a license and the model allows BYOL. You might need to consult a licensing specialist or the vendor to find out whether your existing license applies to the cloud. Security for Data and Applications in the Cloud Introductions to cloud computing typically arrange the functions of an administrator on a stack, with the installation of physical servers and cabling at the bottom of the stack and application management at the top. Managed databases assign responsibility for the bulk of these tasks to the cloud provider, leaving only application-level tasks in the hands of you the client. Self-managed databases keep most tasks in the hands of the client, leaving the vendor mostly to provide physical servers and basic networking. Security tasks also fit this stack concept, leading to what is com‐ monly called a shared security model. The vendor takes on more security tasks in managed databases than in self-managed databases. Briefly put, the cloud provider oversees infrastructure security, but you continue to be responsible for the security of your data and user Security for Data and Applications in the Cloud | 19

Articles in this issue

view archives of APJ - ISV - Database - O'Reilly eBook: An Introduction to Cloud Databases