Examining Cloud Storage Options
i ) Working with object storage
-Much of data storage centers around Objects, a big part of the Cloud Data Store. Now, we will take a look at how objects are typically handled by the various services, benefits you should expect and methodology to look for.Just to be clear, Object : Objects are discrete digital entities, which could mean documents, files, both uncompressed and compressed, images, video, audio, all media.
-Because of the nature of cloud storage, neither quantity nor object file size is a problem- Blobs, Binary Large Objects, are easily accommodated. Many services can handle a single put of any file up to 5 gigabytes in size. Larger files should be split into multiple parts, also known as segmenting and uploaded as part of an overall Object, typically identified with an unique ID.
- Structurally object storage is organized in 2 lavels,
i) Initial layer is the Container. Also called an Asset Group or more commonly a Bucket.
Properties of Container :
~Unlimited Container, You can have as many Containers as you need,
~Each container has an unique ID so that they can be accessed globally. ~Containers are project specific and on all the services it cannot be nested.However, you can usually create folders within the Containers to create a hierarchy.
-For services with multiple data centers around the world, you can specify the region to host the Container. Great for reducing latency to your targeted markets.
ii) Object
Properties :
~Each individual Object is stored within a specific Container,
~Objects cannot be shared across Buckets, although they can be duplicated. Frequently, you'll find the ability to create identifying metadata for your Objects via main value pairs.
~ When the Object is uploaded to the Container, once its integrity is validated, it's available.Similarly, once you delete it, it's no longer accessible there are no undos, so backups are essential.
--Many services offer server-side encryption for security, although you're also free to use client-side encryption prior to transferring the Object. As many Cloud platforms provide a number of varied storage classes with lower costs for data that you don't access as frequently or with as much redundancy.
-Some services, like Google Cloud Storage, apply them at the Container, or Bucket, level. While others, such as Amazon S3 allow you to specify the storage class for individual Objects.
- Once you've set up your Containers and began to populate them with Objects you should ensure that only the people you want to access them can. Object Storage is typically, by default, private and initially only accessible by the owner or primary administrator.
- Permissions can be broadened however all the way up to publicly available. Most services have mechanisms in place for establishing authenticated users. Often via ACLs or Access Control Lists.
-Permissions can be generally applied on the Container level as well as target the Object itself.
- All services provide some API libraries for Object management and many platforms offer a full spectrum of languages from which to choose. Anything from Java to .net to PHP to Python. And with them you can get a full list of your Containers, find out what is in each one and then store, retrieve, copy and delete those Objects. More advanced operations such as targeting specific versions of the Object are available on specific platforms.
-Mastering Containers and Objects is essential to much of productive Cloud Data Storage, Data Record Storage and databases and other systems is another major aspect of the Cloud Data Storage world and one that we will explore next.
Reference : https://www.lynda.com/Cloud-Platform-tutorials/Managing-database-content/383929/432096-4.html
Comments
Post a Comment