Storage & Databases Flashcards
What is the difference between Block Storage and Object Storage?
- Block storage is fixed-sized raw storage capacity
- Block storage stores data in volumes that can be shared and mounted; SAN, iSCSI and local disks
- Block storage is most common for applications and databases
- Object storage does not require a guest OS to exist, accessible via API’s
- Object storage grows as needed
- Object storage is redundant and can be replicated
- Unstructured data like music, image, video
- Log files and database dumps - Large data sets - Archive files
What are all the Google Cloud ‘Storage Options’?
- Cloud Storage - not structured, no mobile sdk
- Cloud Storage for Firebase - not structured, needs mobile sdk
- BigQuery - structured, analytics, read-only
- Cloud Bigtable - structured, analytics, updates with low-latency
- Cloud Datastore - structured, not analytics, non-relational, no mobile sdk
- Cloud Firestore for Firebase - structured, not analytics, non-relational, needs mobile sdk
- Cloud SQL - structured, not analytics, relational, no-horizontal scaling
- Cloud Spanner - structured, not analytics, relational, needs scaling
What are the three blocks that the Internet Assigned Number Authority (IANA) has reserved for private internets?
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
What is persistent disk, it’s features and what is it good/used for?
- Fully-managed, block storage for VM’s and containers
- Good for Compute Engine and Kubernetes Engine
- Good for snapshots of data backup
- Used for VM disks
- Used for sharing read-only data across multiple VMs
Features:
- Durable, independent volumes, 64 TB size, online resize
What is Cloud Storage and what is it good for?
- A scalable, fully-managed, highly reliable, and cost-efficient object / blob store.
- Good for: Images, pictures, and videos, Objects and blobs, Unstructured data
- Workloads: Sotring and streaming multimedia, stroring custom data analytics pipelines
- Achive, backup and disaster recovery
What are the different type of Cloud Storage and what are they good for?
- Multi-Regional: across geographic regions
- Regional: ideal for compute, analytics, and ML workloads in a particular region
- Nearline: backups, low-cost, once a month access
- Coldline: archive, lowest-cost, once a year access
What is Bigtable?
- Massively scalable NoSQL
- Single table that can scale to billions of rows and thousands of columns
- Stores terabytes or petabyes of data
- Ideal for single-keyed data with very low latency
- Ideal data source for MapReduce operations
What is Bigtable good for?
Cloud Bigtable is ideal for applications that need very high throughput and scalability for non-structured key/value data, where each value is typically no larger than 10 MB. Cloud Bigtable also excels as a storage engine for batch MapReduce operations, stream processing/analytics, and machine-learning applications.
You can use Cloud Bigtable to store and query all of the following types of data:
- Marketing data such as purchase histories and customer preferences.
- Financial data such as transaction histories, stock prices, and currency exchange rates.
- Internet of Things data such as usage reports from energy meters and home appliances.
- Time-series data such as CPU and memory usage over time for multiple servers.
What is Cloud Spanner?
- fully-managed, horizontally distibuted relational database service
- handles massive transactional loads
- Uses Paxos algorithm to shard data across hundreds of data centers
- Mission critical, relaional database service with transactional consistency, global scale and high availability
- Cloud Spanner is ideal for relational, structured, and semi-structured data that requires high availability, strong consistency, and transactional reads and writes.
What is Cloud Datastore?
- highly scalable NoSQL ‘document’ database for your applications
- non-relational
- automatic sharding and replication
- highly-available and durable, scales automatically to handle load
- ACID, SQL-like queries, indexes, etc
- RESTful interfaces